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

Ignore env vars for nested executions. #1095

Open
monwolf opened this issue Nov 6, 2024 · 0 comments
Open

Ignore env vars for nested executions. #1095

monwolf opened this issue Nov 6, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@monwolf
Copy link
Contributor

monwolf commented Nov 6, 2024

Hi!
I'm using aws-sso with helm to access a s3 chart repo, and aws-sso for connecting EKS.

So I have to run helm with the env AWS_ACCESS_KEY_ID and it calls aws-sso for doing eks login.
I'm using a kube config global with this configuration for the login:

- name: arn:aws:eks:eu-west-1:xxxx:cluster/xx-devops-xxx-cluster
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1beta1
      args:
      - exec
      - -A
      - "xxxxxx"
      - --role=AdministratorAccess
      - aws
      - eks
      - get-token
      - --cluster-name
      - ae-devops-eks-cluster
      command: aws-sso
      env: null
      interactiveMode: IfAvailable
      provideClusterInfo: false

So when helm run its it shows the error:

error="Conflicting environment variable 'AWS_ACCESS_KEY_ID' is set"

I tried to empty the env var as follows:

      - name: AWS_ACCESS_KEY_ID
        value:

But the same error happens.

How would you be able to solve this? Is there any way to ignore the env vars without doing a wrapper for this command?

@monwolf monwolf added the enhancement New feature or request label Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant