fix: prioritize current-context based on file order #2386
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.
What type of PR is this?
/kind bug
(?)
What this PR does / why we need it:
kubectl config current-context
command retrieves the current-context from the first file with a non-empty value when multiple files are provided. In contrast, config.list_kube_config_contexts() returns the current-context from the last file with a value. Since developers are likely to expect the behavior aligned withkubectl
, I created this PR to adjust the priority.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
I'm guessing that https://github.com/kubernetes/client-go/blob/18a1faa115ed571de5af3e8f0f9c02973769ceb3/tools/clientcmd/loader.go#L246-L273 is relevant, and client-go probably works the same way.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: