Support for pod identity #71
Description
Is your feature request related to a problem? Please describe.
When associating pod identity to aws-fsx-openzfs-csi-driver controller, and then claim PVC, you get the following error:
I0320 10:43:17.281558 1 driver.go:58] "Driver Information" Driver="fsx.openzfs.csi.aws.com" Version="1.1.0"
I0320 10:43:17.281775 1 controller.go:114] "regionFromSession Controller service" region="eu-west-1"
2025/03/20 10:43:17 Ignoring, HTTP credential provider invalid endpoint host, "169.254.170.23", only loopback hosts are allowed. <nil>
E0323 08:45:26.880513 1 driver.go:101] "GRPC error" err=<
rpc error: code = Internal desc = Could not create volume "pvc-6443d867-8267-4f57-b63b-90db383eaec3": 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.
>
E0323 08:45:27.882769 1 driver.go:101] "GRPC error" err=<
rpc error: code = Internal desc = Could not create volume "pvc-6443d867-8267-4f57-b63b-90db383eaec3": 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 the solution you'd like in detail
aws-fsx-openzfs-csi-driver controller should support pod identity and not get this error.
Describe alternatives you've considered
IRSA/OIDC can be used, but it's not optimal.
Additional context
Can be the same issue as -
kubernetes-sigs/aws-fsx-csi-driver#372