Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error getting data key: 0 successful groups required, got 0 #7

Closed
rsmets opened this issue Jan 13, 2021 · 1 comment
Closed

Error getting data key: 0 successful groups required, got 0 #7

rsmets opened this issue Jan 13, 2021 · 1 comment

Comments

@rsmets
Copy link

rsmets commented Jan 13, 2021

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.

repoServer:
  env:
    - name: "AWS_ACCESS_KEY_ID"
      valueFrom:
        secretKeyRef:
          name: "argocd-secret"
          key: "aws.accessKeyId"
    - name: "AWS_SECRET_ACCESS_KEY"
      valueFrom:
        secretKeyRef:
          name: "argocd-secret"
          key: "aws.secretAccessKey"

I have also encrypted a secrets.yaml file in the argocd chart with the following format:

configs:
  secret:
    extra:
      aws.accessKeyId: <Access Key ID>
      aws.secretAccessKey: <Secret Access Key>

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.

@rsmets
Copy link
Author

rsmets commented Jan 14, 2021

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.

@rsmets rsmets closed this as completed Jan 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant