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

Support eks pod identity association #1972

Open
brandocomando opened this issue Dec 12, 2023 · 7 comments
Open

Support eks pod identity association #1972

brandocomando opened this issue Dec 12, 2023 · 7 comments

Comments

@brandocomando
Copy link

What resource do you need?

Aws recently announced eks pod identities. I'd like to use it via crossplane.
https://docs.aws.amazon.com/eks/latest/userguide/pod-id-association.html

Specifically what is missing is the equivalent of this aws CLI command
aws eks create-pod-identity-association --cluster-name my-cluster --role-arn arn:aws:iam::111122223333:role/my-role --namespace default --service-account my-service-account

What is your use case?

Instead of linking service accounts to iam roles via oidc configuration I'd like to use pod identity

Would you be willing to contribute it using code generator

I'll take a look.

@jmalloc
Copy link

jmalloc commented Dec 26, 2023

In addition, it would be great to support pod identities as an authentication method in ProviderConfig

Edit: I made a separate issue for this: #1981

Copy link

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

@github-actions github-actions bot added the stale label Mar 26, 2024
@wesleyorama2
Copy link

/fresh

This is also important to us as well. This is pretty much the only reason we are not using crossplane right now.

Copy link

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

@github-actions github-actions bot added the stale label Jun 25, 2024
@fhochleitner
Copy link

/fresh would love to have this feature

@github-actions github-actions bot removed the stale label Jul 4, 2024
@jmerciercode
Copy link

/fresh

Would be nice

@MisterMX
Copy link
Collaborator

Hey, folks, quick update on the status of this issue:

Since this provider is kind of in maintenance mode and we don't have the time to provide full support we (as maintainers) are not going to implement this and other features on our own. However, we do accept pull requests to include new features into the provider. So feel free to start working on it and assign one of us as reviewer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants