David FryandGitHub 18a5b55839 use env entries instead of envFrom (#36) ...

The reason for this PR is that currently if the secret doesn’t have the
key NB_API_KEY yet at deployment time, the deployment will still run and
pull in an env list that doesn’t include NB_API_KEY since the envFrom
will just pull any and all keys it finds in the secret and makes env
vars out of them. then at a later point, once the NB_API_KEY key is
populated in the secret, one has to bounce the pod to get the key to be
picked up.

if you use the env: valueFrom syntax using a named key, if that named
key doesn’t exist, the deployment should give an error and retry until
the secret key is available

2025-05-01 14:52:03 +02:00

..

kubernetes-operator

use env entries instead of envFrom (#36)

2025-05-01 14:52:03 +02:00