podman kube play should be able to read the bash variables

[antverpp]

Feature request description

For example, I have a number of manifests, where I want to refer some values by an environment variable:
spec:
containers:

• name:
  image: ${REGISTRY}/:${TAG}

where REGISTRY and TAG are defined as env variables, for example in the .env file.

Suggest potential solution

A clear and concise description of what you want to happen.

Have you considered any alternatives?

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

[antverpp]

A clear and concise description of what you want to happen:
So, I define variables in .env file.
And I refer them in the manifest, as described above.
Like, REGISTRY=myregistry.com, TAG=0.0.1

And as a result, the podman play kube should render the manifest and pull the image myregistry.com/myname:0.0.1,
being defined in the yaml manifest as "image: ${REGISTRY}/myname:${TAG}"

[rhatdan]

Interested in opening a PR to make this happen?

[giuseppe]

Does Kubernetes support it?

[roman-kiselenko]

Kubernetes YAML doesn't support this kind of variable interpolation.
You can achieve the same thing with envsubst

# my_pod.yaml
apiVersion: v1
kind: Pod
metadata:
  name: foobar
spec:
  containers:
  - name: container-1
    image: ${REGISTRY}/${REPO}:${TAG}

REGISTRY=myregistry.com REPO=project TAG=0.0.1 envsubst < my_pod.yaml > pod.yaml

# pod.yaml
apiVersion: v1
kind: Pod
metadata:
  name: foobar
spec:
  containers:
  - name: container-1
    image: myregistry.com/project:0.0.1

[antverpp]

Does Kubernetes support it?

Well, at least the well-known RedHat product can do it pretty well: oc process --param-file=test.env -f test.yaml | oc create -f -

[rgprajeen]

So, can't this be achieved by using sed? Like using a format like __VARNAME__ in the yaml file and later generating a new yaml using sed -i "s|__VARNAME__|${VARNAME}|g"

[github-actions]

A friendly reminder that this issue had no activity for 30 days.

[rhatdan]

Since we have not heard back, closing. Reopen if you have more feedback.