kubectl: check rule in exec command is insecurity

[hunshcn]

What happened?

https://github.com/kubernetes/kubernetes/blob/b53b9fb5573323484af9a19cf3f5bfe80760abba/staging/src/k8s.io/kubectl/pkg/cmd/exec/exec.go#L208-L215

kubectl exec -it resource asd asd asd -- bash will be like kubectl exec -it resource -- bash but no error

This can lead to unexpected behavior of command with --

What did you expect to happen?

raise error error: exec [POD] [COMMAND] is not supported anymore.

How can we reproduce it (as minimally and precisely as possible)?

kubectl exec -it resource asd asd asd -- bash

Anything else we need to know?

No response

Kubernetes version

$ kubectl version
v1.32.3

Cloud provider

-

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[hunshcn]

/sig cli

[hunshcn]

/assign

[mbergo]

/assign