Closed irmiller22 closed 3 years ago
@irmiller22 - I think this meant to be passed as a flag only, e.g. I've updated config with:
...
- image: upmcenterprises/registry-creds:1.10
args:
- --aws-secret-name
- my-aws-creds-secret
...
... and I see my-aws-creds-secret
gets created.
time="2021-08-10T22:38:03Z" level=info msg="Created new secret my-aws-creds-secret in namespace default" function=processNamespace
time="2021-08-10T22:38:03Z" level=info msg="Updating ServiceAccount default in namespace default" function=processNamespace
time="2021-08-10T22:38:03Z" level=info msg="Finished processing secret for namespace default, secret my-aws-creds-secret"
$ kubectl get secrets
NAME TYPE DATA AGE
acr-secret kubernetes.io/dockerconfigjson 1 71s
dpr-secret kubernetes.io/dockerconfigjson 1 72s
my-aws-creds-secret kubernetes.io/dockerconfigjson 1 72s
...
@antonblr ah, good catch. Thanks for correcting me. I'll close the issue now.
I tried setting up my
deployment.yaml
configuration to set theaws-secret-name
value, but the secret is always set to the default valueawsecr-cred
despiteaws-secret-name
being set.The
deployment.yaml
file looks like the following:My secrets file looks like the following:
The other variables (
AWS_ACCESS_KEY_ID
,AWS_SECRET_ACCESS_KEY
,aws-account
,aws-region
) are recognized, butaws-secret-name
isn't.Here's the log output after deployment: