You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
k9s command: deployments
stays empty
whereas I am able to get deployments kubectl get deploy -A kubectl get deployments --all-namespaces
on a specific namespace kubectl get deployment -n kube-system
To Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Versions (please complete the following information):
OS: Linux Amazon 2023 Fedora like
K9s: v0.27.4
K8s: v1.24.14-eks-c12679a
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
good92
changed the title
deployments are not showing up whereas kubctl gives a list
deployments are not showing up whereas kubectl gives a list
Jun 15, 2023
good92
changed the title
deployments are not showing up whereas kubectl gives a list
deployments are not showing up, whereas kubectl gives a list
Jun 15, 2023
typing: deploy works, typing: deployments does not work.
Thanks for this great tool anyway.
I am wondering if have a one click sidecar 'curl' tester activator, would be a good idea in order to achieve easy network ingress validation.
Describe the bug
k9s command: deployments
stays empty
whereas I am able to get deployments
kubectl get deploy -A
kubectl get deployments --all-namespaces
on a specific namespace
kubectl get deployment -n kube-system
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Versions (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: