[RFE] Ability to specify additional JSONPatch operations for transform

[knandras]

What is your persona?

I'm a cluster administrator for several clusters with a high level of privilege. I need to export, clean and re-deploy applications between stages/clusters quite regularly.

What is your story / use case?

As an administrator, I want to be able to specify additional JSONPatch operations, so that I can remove additional cluster/Rancher-specific fields from the transformed manifests.

We use Rancher to manage our K8S Clusters, and Rancher has its own set of annotations that are sometimes embedded in .spec.template.metadata.annotations. I need to remove these fields to get a clean manifest for re-deployment in another cluster.

We often have developers build an application or middleware deployment in a testing cluster, and we need to export the manifests, clean them, and create modules for later reuse.

If JSONPatch tests could be used to skip execution on a per-manifest basis (instead of the whole crane apply operation), that would be welcome.

Do you have a suggestion for implementation?

An additional flag for crane transform that points to a file/directory containing JSONPatch operations.

[github-actions]

This issue is currently awaiting triage.
If contributors determine 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.