Tim Bannister
Tim Bannister
This is a kubectl issue /transfer kubectl
Prompted by https://github.com/kubernetes/website/issues/33764
I believed that `kubectl version -oyaml --client` is deprecated because `--client` is deprecated. However, if `--client` is only deprecated for the default output format then these both work: ```shell kubectl...
Actually, we could mention that both - `kubectl version --client -ojson | jq -r .clientVersion.gitVersion` - `kubectl version -oyaml --client|awk '/gitVersion/{print $2;}'` are viable options, and let users choose.
It sounds like this is expected behavior, and that we should document the warning as something for readers to be aware of and ignore if they are deploying v1.24 `kubectl`.
> the flag --client is not deprecated ``` $ kubectl version --client WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use...
This looks like a feature request for kubectl (which might then trigger a request for machine-readable mutability marking in the OpenAPI, I'm not sure) /transfer kubectl
/transfer kubectl
/sig security
Because I like to work in a blameless / mistakes-are-OK culture, I'd prefer to have a different subcommand name than `blame`. It's OK for `blame` to be a shorthand for...