You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upon following the README steps very closely I am seemingly stuck on retrieving the key for KMS from within argo. I am trying to deploy a custom chart.
I have added the following to my argocd's chart values.yaml.
I have installed helm-sops locally and I have tested decrypting and encrypting with the IAM user which those AWS access creds relate to. The output of helm-sops template ... on my host machine properly handles decrypting the secrets.yaml file of the target chart I am trying to use.
The error seems to point towards not being able to retrieve the KMS key from within the argo-server (which was deployed with the argocd chart with the special configs mentioned above).
Upon inspection of the argocd-repo-server pod (created as a result on the chart install) I actually do not see the env var AWS_ACCESS_KEY_ID or AWS_SECRET_ACCESS_KEY. I feel like I should? i.e. the results of kubectl exec -n argocd argocd-repo-server-64bf999468-ls6m9 -- printenv does not yield the vars above.
The text was updated successfully, but these errors were encountered:
Ahh config error my side. I did not preface my argo-cd chart values with the argo-cd chart name. Closing. Everything is working great!! Thanks for this killer project.
Upon following the README steps very closely I am seemingly stuck on retrieving the key for KMS from within argo. I am trying to deploy a custom chart.
I have added the following to my argocd's chart values.yaml.
I have also encrypted a secrets.yaml file in the argocd chart with the following format:
I have installed
helm-sops
locally and I have tested decrypting and encrypting with the IAM user which those AWS access creds relate to. The output ofhelm-sops template ...
on my host machine properly handles decrypting the secrets.yaml file of the target chart I am trying to use.The error seems to point towards not being able to retrieve the KMS key from within the argo-server (which was deployed with the argocd chart with the special configs mentioned above).
Upon inspection of the
argocd-repo-server
pod (created as a result on the chart install) I actually do not see the env varAWS_ACCESS_KEY_ID
orAWS_SECRET_ACCESS_KEY
. I feel like I should? i.e. the results ofkubectl exec -n argocd argocd-repo-server-64bf999468-ls6m9 -- printenv
does not yield the vars above.The text was updated successfully, but these errors were encountered: