Closed warjiang closed 3 months ago
This issue is currently awaiting triage.
SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted
label.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
This issue is not a kubectl
issue, many commands have the same issue when using ohmyzsh
, did you consider this comment?
https://github.com/ohmyzsh/ohmyzsh/issues/31#issuecomment-359728582
unsetopt nomatch
This issue is not a
kubectl
issue, many commands have the same issue when usingohmyzsh
, did you consider this comment? ohmyzsh/ohmyzsh#31 (comment)
unsetopt nomatch
yeah, maybe the maintainer of kubectl can update the example, this will be useful for people who not very familiar with kubectl. When i first use kubectl debug command, it make me confused.
Going to close the issue but we would accept a PR if you want to make one and tag me.
/close
@eddiezane: Closing this issue.
What would you like to be added:
change the example of set-image option
Why is this needed:
when i follow the examples in![image](https://github.com/kubernetes/kubectl/assets/6478745/9a9ae41e-da83-4910-9691-af9eaa0163cc)
kubectl debug -h
, when i try to set-image for debug containers, a mistake occured like following:and i found a releated issue of ohmyzsh: https://github.com/ohmyzsh/ohmyzsh/issues/31 after add double quote, it worked as expecte.![image](https://github.com/kubernetes/kubectl/assets/6478745/76dd962d-89d2-4a15-8e5c-a034baa6a9a4)
so i suggest that correct the example.