Enhancement: put path/type in json patch rather than in kustomization.yaml

[donbowman]

Currently we have json patches split into two spots (kustomization.yaml and the patch itself):

patchesJson6902:
  - target:
      version: v1
      kind: Service
      name: nginx-ingress-controller
    path: controller-service.yaml

  - target:
      group: extensions
      version: v1beta1
      kind: Deployment
      name: nginx-ingress-controller
    path: controller-deployment.yaml

...
---
- op: add
  path: /spec/ports/-
  value: {"name": "24224-tcp", "port": 24224, "protocol": "TCP", "targetPort": "24224-tcp"}
- op: replace
  path: /spec/loadBalancerIP
  value: "52.167.3.63"

This makes it hard to manage (since i'm often making a similar patch to 2 or more base files). It would be simpler if the type/path was in the patch, like below.

E.g. when changing a containerPort across the deployment + service + ingress, its easier to manage a single file called 'change the port' than 3 files + the config in the kustomization.yaml.

---

 kind: Service
 name: foo
 patch:
   - op: add
     path: /spec/ports/-
     value: {"name": "24224-tcp", "port": 24224, "protocol": "TCP", "targetPort": "24224-tcp"}
   - op: replace
     path: /spec/loadBalancerIP
     value: "52.167.3.63"

---
 kind: extensions/v1beta1
 name: foo
 patch:
   - op: replace
     ...

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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/test-infra repository.

[marshallford]

Is there an example of how to move the target data into the patch file now that #1355 is merged?