Closed warjiang closed 4 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.
I think, this will be handled by this feature https://github.com/kubernetes/enhancements/issues/4292.
and this is the duplicate of https://github.com/kubernetes/kubectl/issues/1506
and this is the duplicate of #1506
yes! it's exactly what I wanted
I think, this will be handled by this feature kubernetes/enhancements#4292.
em, new to kubernetes community, and how, it's not a breaking change, maybe you can copy the copy or just cherry-pick the commit, anyway is ok for me 😃
I think, this will be handled by this feature kubernetes/enhancements#4292.
@ardaguclu hi~ I'm new to kubernetes community, what should I do to make this change into KEP4292, making comments in https://github.com/kubernetes/enhancements/issues/4292 ? any suggestions or advices 😃
@warjiang thanks for your enthusiasm. You'll get this feature for free, when this PR https://github.com/kubernetes/kubernetes/pull/120346 merges.
I'm closing this as it has already been marked as duplicate. /close
@ardaguclu: Closing this issue.
I'm closing this as it has already been marked as duplicate. /close
ok. i'll close this pr in main repo of kubernetes https://github.com/kubernetes/kubernetes/pull/123581
thanks for your reply as well 😄
What would you like to be added: add
imagePullSecrets
for debug likeWhy is this needed: in case of enterprise, private registry is the first choice, if execute
kubectl debug node/mynode -it --image=${registry}/busybox
it will report image pull error, so we need addimagePullSecrets
options.