Support kubectl config get-contexts JSON output
#1614
Comments
|
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 |
|
/assign |
|
Is this still being worked on? I want to create a PR for this. |
|
/retitle Support |
kubectl config get-contexts JSON output
|
I will finish this. /assign |
|
This was discussed during SIG-CLI on 5/28, and based on further investigation we agreed that the functionality proposed is already available through: kubectl config view -o jsonpath='{.contexts}' |
|
We are not planning to add this functionality for now |
|
@ardaguclu: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
What would you like to be added:
Please add support for
config get-contextsJSON output.Why is this needed:
Currently,
config get-contextscan 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: