✨ feat(kube): add --print-path flag to cluster kubeconfig - #346
Merged
Merged
Conversation
|
WARNING : Differences in reference doc 🤔 Detailed changesdocs/reference/octl_kube_cluster_kubeconfig.md |
|
🔖 auto-tagging: Adding label "kind/feature" |
|
No flags have been deleted 😀 |
|
Binary size: 82.3MB => 82.3MB (change +8KB, +0.0%) 😉 |
jobs62
approved these changes
Sep 21, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR adds a
--print-pathflag tocluster kubeconfig.This is implemented as a print-path formatter that caches the output to a file in ~/.cache and displays the path of the file.
It can be used on all commands but is only exposed/documented in
cluster kubeconfig.An alternative could have been to develop an ad-hoc kubeconfig command, using the same kubeconfig cached file as
cluster kubectl. This solution was not used because:cluster kubeconfighas flags controlling the content of the kubeconfig (user, group, ttl),Type of Change
Please check the relevant option(s):
How Has This Been Tested?
Please describe the test strategy:
Checklist
Additional Context