Can I please check, should The key/vaue pairs in a RuntimeEnvironment file passed to gravity install with —config get set as environment variables in all of the containers of my deployment?
When I exec in using kubectl exec bash I am not seeing them set.
I am hoping to use this strategy to pass in bare metal deployment configuration.
If container env setting is supposed to happen via a RuntimeEnvironment it must be a problem at my side, but the docs aren’t 100% conclusive that this is the intention. The docs mention the master ‘planet’ container has these environment variables, so I am not sure if my deployment containers will also have them set.
I do hope that this is the intention, as I can’t see another route to getting install-specific config into the deployment.
This is the install command that I am using:
./gravity install --advertise-addr=$WAN_IP --token=abcdef --config=envars.yaml
And this is the contents of envars.yaml:
kind: RuntimeEnvironment version: v1 spec: data: SITE_CODE: "xxx" API_KEY: "yyy" MQ_PASSWORD: "zzz"
I can’t see any of $SITE_CODE, $API_KEY or $MQ_PASSWORD in my containers.
All help appreciated. Thanks in advance!