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
Is your feature request related to a problem? Please describe.
Teammate installed "Argones" in the cluster, don't know if Argones itself is buggy or it was a poorly-done install. "kubectl api-resources" gives a list of resources, nonzero exit, and writes to stderr "error: unable to retrieve the complete list of server APIs: allocation.agones.dev/v1: the server is currently unable to handle the request". When I launch kubecom, I see the error at the bottom of the screen, briefly, and the left-hand column for browsing resources does not appear. "F2" to choose namespaces still works, so I know kubecom can talk to the cluster.
Describe the solution you'd like
left-hand column still shows the resources reported by "kubectl api-resources" that also appear in ~/.kubecom.yaml (or the default list if this file is missing)
Describe alternative solutions you've considered
Find the co-worker who installed "Argones," and tell them to always test in an alpha environment first.
Additional context
This is a feature request because it's not a bug in kube-commander -- I'm asking for more tolerance in kube-commander for bugs in other software.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Teammate installed "Argones" in the cluster, don't know if Argones itself is buggy or it was a poorly-done install. "kubectl api-resources" gives a list of resources, nonzero exit, and writes to stderr "error: unable to retrieve the complete list of server APIs: allocation.agones.dev/v1: the server is currently unable to handle the request". When I launch kubecom, I see the error at the bottom of the screen, briefly, and the left-hand column for browsing resources does not appear. "F2" to choose namespaces still works, so I know kubecom can talk to the cluster.
Describe the solution you'd like
left-hand column still shows the resources reported by "kubectl api-resources" that also appear in ~/.kubecom.yaml (or the default list if this file is missing)
Describe alternative solutions you've considered
Find the co-worker who installed "Argones," and tell them to always test in an alpha environment first.
Additional context
This is a feature request because it's not a bug in kube-commander -- I'm asking for more tolerance in kube-commander for bugs in other software.
The text was updated successfully, but these errors were encountered: