[Question] How can i use variables in kustomization.yaml file

[Kristin0]

For example i want in file
kustomization.yaml smth like this

resources:
  - deployment.yaml
namespace: $(namespace)

vars:
  - name: namespace
    objref:
      kind: ClusterContext
      name: clustercontext
      apiVersion: msc.test.com/v1alpha1
    fieldref:
      fieldpath: spec.TEST_NAMESPACE

[k8s-ci-robot]

@Kristin0: This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[tdi]

hi @Kristin0 I think having variables like that is against the kustomize principles of having clean builds (https://kubectl.docs.kubernetes.io/faq/kustomize/eschewedfeatures/#build-time-side-effects-from-cli-args-or-env-variables).

You can use something like that kustomize edit set namespace $NAMESPACE_FROM_ENV if namespace is in metadata field it will be effective.

[Kristin0]

Ok, thanks

[KnVerey]

@tdi is correct. Variables go against a core goal of Kustomize, namely to provide a template-free solution. The "vars" feature you referenced does not really work like variables and is being removed in favour of replacements. #4049

/triage out-of-scope
/close

[k8s-ci-robot]

@KnVerey: Closing this issue.

In response to this:

@tdi is correct. Variables go against a core goal of Kustomize, namely to provide a template-free solution. The "vars" feature you referenced does not really work like variables and is being removed in favour of replacements. #4049

/triage out-of-scope
/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.

[mtrin]

@KnVerey
Does it mean this documentation is out of date?
What is the official, most up-to-date documentation source for Kustomize?
Thanks!

[KnVerey]

At a glance that doc looks fine to me, but is about advanced transformer configuration. It does mention the existing vars feature (which as mentioned above is not actually variables, despite the name) as an example; that feature is being deprecated but still works in current versions, as advised in the linked doc. The best docs for Kustomize are currently in the SIG CLI site: https://kubectl.docs.kubernetes.io. There is a slowly progressing initiative to consolidate the various sources into a dedicated site: #4338.