Replies: 2 comments 1 reply
-
This is simply not possible with What is commonly done instead is to use the - op: test
path: /spec/template/spec/containers/0/env/1/name
value: TRACING_COLLECTOR_HOST
- op: replace
path: /spec/template/spec/containers/0/env/1/value
value: newvalue You should probably also add a |
Beta Was this translation helpful? Give feedback.
1 reply
-
you can use replacements with a local configmap (config.kubernetes.io/local-config: true) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Given this YAML file, what would be the proper syntax to patch the value of the
env
element that hasTRACING_COLLECTOR_HOST
asname
?This works, but hardcodes "use the second element in the list" (
.../env/1/...
):I find no syntax that kustomize accepts, that lets me define this. Is this possible?
The RFCs for JSON patches contain only very basic paths, unfortunately.
yq
accepts something like this:Here are some of the things I tried with kustomize:
Beta Was this translation helpful? Give feedback.
All reactions