Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: recover from "kubectl api-resources" errors #87

Open
mozai opened this issue Dec 10, 2020 · 0 comments
Open

Feature: recover from "kubectl api-resources" errors #87

mozai opened this issue Dec 10, 2020 · 0 comments

Comments

@mozai
Copy link

mozai commented Dec 10, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant