kubectl: support creating immutable secrets and configmaps

[kplachkov]

What would you like to be added?

Support for creating immutable Secrets and ConfigMaps to kubectl.

Why is this needed?

This is needed to improve the UX.

[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.

[kplachkov]

/sig cli

[googs1025]

/transfer kubectl

[ardaguclu]

Preparing a resource yaml containing all the required fields (including the immutable field is set to true) and after that, applying this resource via kubectl apply is the recommended path.

I don't think, we'd add more flags into these implicit commands. It is better to close this issue.

[ardaguclu]

/close

[k8s-ci-robot]

@ardaguclu: Closing this issue.

In response to this:

/close

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.

[kplachkov]

Preparing a resource yaml containing all the required fields (including the immutable field is set to true) and after that, applying this resource via kubectl apply is the recommended path.

Hmm, I wonder why kubectl has all those other commands and flags if it’s just about kubectl apply? "Recommended path" means it’s not the only path, right?