JSONPatch annotations containing slashes

[benjamin-bergia]

Not really a Kustomize issue but we definitely need a work around.

When patching annotations, it happens that the keys contain /. Like for example when patching my ingress:

- op: add
  path: /metadata/annotations/traefik.ingress.kubernetes.io/redirect-permanent
  value: false

This doesn't work since it should be interpreted as

metadata:
  annotations:
    traefik.ingress.kubernetes.io/redirect-permanent: false

But is actually interpreted as:

metadata:
  annotations:
    traefik.ingress.kubernetes.io:
      redirect-permanent: false

[dbarrosop]

Is there an actual solution for this? I am having the same problem

[benjamin-bergia]

Yep, it's part of jsonpatch http://jsonpatch.com/#json-pointer

[tkellen]

Just to put the solution right here directly, use ~1 to represent a /

[RobertDiPaolo]

It also seems that you need to quote the path if you use the ~1 escape, e.g.

- op: add
  path: "/metadata/annotations/traefik.ingress.kubernetes.io~1redirect-permanent"
  value: false

[John-Lin]

how come the docs describe that put a \ before /?

Kustomize supports escaping special characters in path, e.g metadata/annotations/foo.k8s.io/bar
https://github.com/kubernetes-sigs/kustomize/tree/master/examples/transformerconfigs#supporting-escape-characters-in-crd-path

see #907

[Shell32-Natsu]

@John-Lin JSON patch itself has its own definition and implementation. It's irrelevant from how kustomize handle the slash.