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

Provide better error messages when access to the Kubernetes clusteres has expired #232

Open
odedia opened this issue Dec 21, 2021 · 0 comments

Comments

@odedia
Copy link

odedia commented Dec 21, 2021

When running kp import (and possibly other commands) against a Kubernetes cluster, and the access to that cluster is blocked/expired/invalid, the response could be misleading.

In the case of kp import, the response is failed to get default repository, use "kp config default-repository" to set...

When running a simple command such as kubectl get pods against the same expired cluster, the error would be Unauthorized.

The error in kp could be misleading and make users search for issues that are unrelated to the access problem, so it's best to have a good error message to indicate it instead.

Thanks.

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