Open heroes1412 opened 3 weeks ago
Hi @heroes1412
The patches.path
in kustomize is using Patch Strategic Merge method that is used in kubect.
When we want to merge a list in K8s resources, kustomize check "x-kubernetes-patch-strategy" anchor in the API definition in the kubernetes. (like here)
But ingress looks like no anchors that referred from kustomize and kustomize can't merge lists and try to replace all items.
So, Could you consider using a JSON6902-style patch? You can patch for resources what you want to do.
/triage out-of-scope /kind needs-information
@koba1t: The label(s) kind/needs-information
cannot be applied, because the repository doesn't have them.
What happened?
i try to create a ingress-patch.yaml file, to patch some value, i found spec.rules.http.paths.backend.service.port and spec.rules.http.paths.backend.service.port.number is not inherited from the base
What did you expect to happen?
spec.rules.http.paths.backend.service.port and spec.rules.http.paths.backend.service.port.number is inherited from the base
How can we reproduce it (as minimally and precisely as possible)?
Expected output
service.port of ingress resource will be inherited from the base.
Actual output
Kustomize version
v5.4.2
Operating system
Linux