vars replacement overview #5046
Replies: 3 comments 2 replies
-
I think there was a saying: if KRM function is your sledge hammer then every problem is a nail! Well maybe not exactly, but something along these lines... ;-P |
Beta Was this translation helpful? Give feedback.
-
+1 |
Beta Was this translation helpful? Give feedback.
-
A way to define common variables is such a common requirement that all my kustomize based setups (with or without ArgoCD) have always had a companion envsubst mechanism. it would be great if kustomize offered a mechanism of its own - without having to eg generate an extra configmap just to be able to use the awkward Replacements feature. |
Beta Was this translation helpful? Give feedback.
-
Background:
I read in the kustomize v5 release notes and open issue #4049 that the entire
vars
feature is deprecated, and that we are advised to usereplacements
instead.Unfortunately, if I understand correctly, replacements cannot replace all uses of vars, but there are several proposals to address some of the deficits: #3787 #4517
However, even these proposals do not completely fill the gap because they target structured data, whereas vars supports string replacement.
Another issue with
replacements
is that it does not compose in the same way thatvars
does, so it may not be possible to replace a Component using vars with one using replacements: #4099 (comment)Questions:
Is this a fair summary?
What is the strategy for resolving this impasse? I only see a deprecation notice, a partial alternative, and several (incomplete) proposals.
Am I missing something? Where can I find more discussion?
Beta Was this translation helpful? Give feedback.
All reactions