-
Notifications
You must be signed in to change notification settings - Fork 923
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
Support kubectl config get-contexts
JSON output
#1614
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Comments
hclihn
added
the
kind/feature
Categorizes issue or PR as related to a new feature.
label
Jun 25, 2024
k8s-ci-robot
added
the
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
label
Jun 25, 2024
Sounds to me a reasonable ask. |
I'll take a look at this. |
@ah8ad3 before working on it, I think it would be better to wait bug scrub to triage it first. |
/triage accepted |
k8s-ci-robot
added
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
and removed
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
Jul 17, 2024
/assign |
Is this still being worked on? I want to create a PR for this. |
/retitle Support |
k8s-ci-robot
changed the title
Support config get-contexts JSON output
Support Aug 8, 2024
kubectl config get-contexts
JSON output
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
What would you like to be added:
Please add support for
config get-contexts
JSON output.Why is this needed:
Currently,
config get-contexts
can only output column-oriented format or the name field (using-o=name
). However, when the cluster/context name contains space(s) which is true for our company's implementation, it makes the parsing of the output very challenging. If the command output can support a JSON format, then it's relatively easier to use existing tools to parse it, regardless if the cluster/context name contains space(s) or not.The text was updated successfully, but these errors were encountered: