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

Skaffold- Could not connect to kubernetes cluster should report a distinct exit code. #4645

Closed
tejal29 opened this issue Aug 10, 2020 · 0 comments · Fixed by #4933
Closed
Assignees
Labels
kind/friction Issues causing user pain that do not have a workaround priority/p1 High impact feature/bug.
Milestone

Comments

@tejal29
Copy link
Member

tejal29 commented Aug 10, 2020

Skaffold dev, deploy, should return an distinct error code when kubernetes cluster could not be reached.

"Unable to connect to Kubernetes cluster. Get "x.x.x.x"

Skaffold dev should not try to clean up when we exit due to the above error code.

@tejal29 tejal29 added kind/friction Issues causing user pain that do not have a workaround priority/p1 High impact feature/bug. labels Aug 10, 2020
@nkubala nkubala added this to the Backlog milestone Sep 1, 2020
@PriyaModali PriyaModali modified the milestones: Backlog [P0/P1], v1.16.0 Oct 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/friction Issues causing user pain that do not have a workaround priority/p1 High impact feature/bug.
Projects
None yet
3 participants