Show patch strategy in `kubectl explain`

[xlucas]

What would you like to be added?

Show patch strategy metadata (ie patchStrategy, patchMergeKey and so on as covered in https://kubernetes.io/docs/tasks/manage-kubernetes-objects/update-api-object-kubectl-patch) in kubectl explain.

Why is this needed?

This information is very important to users since it could lead to unexpected results while patching object fields but alas only shown in the full API reference. It'd be helpful to see it with kubectl explain directly.

[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/test-infra repository.

[pranav-pandey0804]

/sig cli

[pranav-pandey0804]

Hi @xlucas ,
Great idea on enhancing kubectl explain with patch strategy info. This could clarify resource updates for users. Suggesting a discussion in SIG CLI to gather more insights and potentially refine this idea. I'm interested in how this evolves and may contribute as it moves forward.

[ah8ad3]

Hi folks,
I was also looking at the issue and in middle of checking the kubectl explain i saw and message in
kubectl explain deployment.spec.template.spec
due to update-api-object-kubectl-patch we can add new containers via different patch strategies but in message this is what i saw

  containers	<[]Container> -required-
    List of containers belonging to the pod. Containers cannot currently be
    added or removed. There must be at least one container in a Pod. Cannot be
    updated.

also i can help with resolving this issue if it get triange accepted.

[HirazawaUi]

/transfer kubectl

[mpuckett159]

This sounds great. Thank you for helping update the explain outputs.
/triage accepted

[ah8ad3]

/assign