Requesting support for EKS Pod Identity
git4example opened this issue · 3 comments
Is your feature request related to a problem?/Why is this needed
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
/feature
Describe the solution you'd like in detail
A clear and concise description of what you want to happen.
Currently FSX CSI Driver on EKS cluster (tested on 1.29 using master branch v1.1.0) is not supporting Pod Identity (https://docs.aws.amazon.com/eks/latest/userguide/pod-identities.html)
It fails with error
>
E0208 06:12:08.238251 1 driver.go:104] "GRPC error" err=<
rpc error: code = Internal desc = Could not create volume "pvc-1c046e87-ba4f-40e1-af52-44d138ce0d50": CreateFileSystem failed: NoCredentialProviders: no valid providers in chain
caused by: EnvAccessKeyNotFound: failed to find credentials in the environment.
SharedCredsLoad: failed to load profile, .
CredentialsEndpointError: invalid endpoint host, "169.254.170.23", only loopback hosts are allowed.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Had to use IRSA.
Additional context
Add any other context or screenshots about the feature request here.
From my understanding, this is purely due to the aws-sdk-go version being used in the v1.1.0 driver. Here's a PR with some more info: #371. We plan to release v1.2.0 by the end of this week, after which you should be able to use pod identity as expected. Will close this issue once v1.2.0 is released
v1.2.0 has been released, which included an updated sdk-go version. Please reopen if you encounter pod identity issues with the new csi driver version
/close
@jacobwolfaws: Closing this issue.
In response to this:
v1.2.0 has been released, which included an updated sdk-go version. Please reopen if you encounter pod identity issues with the new csi driver version
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.