Fixed error on missing config references #425
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It is possible for kube config file to contain a context that refers to cluster or user configurations that don't exist. I don't know how, but my kubeconfig file does, and even when I clean it up, this frequently happens. These contexts are old contexts that I don't use anymore, so they are safe to ignore. kubectl just ignores them. Skuber should do the same.
doriordan
pushed a commit
that referenced
this pull request
Nov 10, 2025
It is possible for kube config file to contain a context that refers to cluster or user configurations that don't exist. I don't know how, but my kubeconfig file does, and even when I clean it up, this frequently happens. These contexts are old contexts that I don't use anymore, so they are safe to ignore. kubectl just ignores them. Skuber should do the same.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It is possible for kube config file to contain a context that refers to cluster or user configurations that don't exist. I don't know how, but my kubeconfig file does, and even when I clean it up, this frequently happens. These contexts are old contexts that I don't use anymore, so they are safe to ignore. kubectl just ignores them. Skuber should do the same.