UNCLASSIFIED - NO CUI

Skip to content
Snippets Groups Projects

ArgoCD - AWS credentials aren't mounted into the repoServer deployment

    • Closed Issue created by adam.toy @adam.toy1

    Bug

    Description

    When specifying AWS credentials using the chart's values, the argocd-iam-secret gets created:

    addons:
  argocd:
    values:
      awsCredentials:
        awsAccessKeyId: "REDACTED"
        awsSecretAccessKey: "REDACTED"

    However, that secret doesn't get mounted into the repoServer deployment. We've had to work around it by adding the following:

    repoServer:
  env:
  - name: AWS_ACCESS_KEY_ID
    valueFrom:
      secretKeyRef:
        name: argocd-iam-secret
        key: AWS_ACCESS_KEY_ID
  - name: AWS_SECRET_ACCESS_KEY
    valueFrom:
      secretKeyRef:
        name: argocd-iam-secret
        key: AWS_SECRET_ACCESS_KEY
  - name: AWS_DEFAULT_REGION
    valueFrom:
      secretKeyRef:
        name: argocd-iam-secret
        key: AWS_DEFAULT_REGION

    Ideally these ENVs would get mounted conditionally if the awsCredentials are provided.

    BigBang Version

    1.27.1

    Designs

      Child items 0

      2. No child items are currently assigned. Use child items to break down this issue into smaller parts.

      Activity

      Please register or sign in to reply

      UNCLASSIFIED - NO CUI