Skip to content
New issue

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

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

Already on GitHub? # to your account

[Bug] eksctl create podidentityassociation does not support --profile flag #8016

Open
skubot opened this issue Oct 23, 2024 · 6 comments
Open
Labels

Comments

@skubot
Copy link

skubot commented Oct 23, 2024

Hi there, we use SSM session manager... so to create a cluster I need to supply the --profile flag eg:
eksctl create cluster -f cluster.yaml --profile ${PROFILE}

Now I want to create an EKS pod identity association using:
eksctl create podidentityassociation -f cluster.yaml --profile ${PROFILE}
However then I get this error:

Error: unknown flag: --profile

Is it possible to support profile flag in create podidentityassociation sub-command?

Thanks

Versions

eksctl version: 0.191.0
kubectl version: v1.27.2
OS: darwin
Copy link
Contributor

Hello skubot 👋 Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-5 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl on our website

@skubot
Copy link
Author

skubot commented Oct 23, 2024

Maybe this is not a bug, maybe a feature request? ...but wouldn't it make sense for all eksctl sub-commands to support the --profile flag?

@geocomm-shenningsgard
Copy link

Just noticed this today as well for eksctl get podidentityassociation

@cPu1
Copy link
Contributor

cPu1 commented Nov 1, 2024

Maybe this is not a bug, maybe a feature request? ...but wouldn't it make sense for all eksctl sub-commands to support the --profile flag?

@skubot, yes, this was probably an oversight. --profile should be supported by all eksctl commands that query Kubernetes or invoke the AWS API. In the meantime, I'd recommend working around it by passing the AWS_PROFILE environment variable.

@skubot
Copy link
Author

skubot commented Nov 10, 2024

Thanks @cPu1 setting AWS_PROFILE works. Hopefully --profile gets supported across the board.

@sbaugh-rh
Copy link

Just ran across this, as well. Any chance that the fix for this is in the queue?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants