[RFC-0010] Remove EKS Pod Identity from the proposal #5309
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
matheuscscp
force-pushed
the
update-rfc-0010
branch
from
3f89c85 to
0daa31c
Compare
stefanprodan
approved these changes
Apr 29, 2025
Signed-off-by: Matheus Pimenta <[email protected]>
matheuscscp
force-pushed
the
update-rfc-0010
branch
from
0daa31c to
c18ab38
Compare
71 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While testing the RFC implementation I got blocked by the fact that we try to create the
ServiceAccounttoken bound to a pod in order to support EKS Pod Identity, which has this requirement. The only pod we can be sure exists is the controller pod itself, so we use theos.Getenv("HOSTNAME")environment variable. However, the Kubernetes API does not accept issuing aServiceAccounttoken bound to a pod that does not use thatServiceAccount.Conclusion: It's impossible to support EKS Pod Identity for multi-tenant workload identity, it works only for the single-tenant version. We can only support IRSA for multi-tenant workload identity.