Skip to content

node cannot read region from ec2 metadata #429

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

Open
coolstim opened this issue May 15, 2025 · 1 comment · May be fixed by #430
Open

node cannot read region from ec2 metadata #429

coolstim opened this issue May 15, 2025 · 1 comment · May be fixed by #430
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@coolstim
Copy link

/kind bug
The region for the node is not settable via the helm chart.
For the controller the region can be set via the helm chart, for the node this is not the case leading to

driver.go:62] "Driver Information" Driver="fsx.csi.aws.com" Version="v1.4.0"
metadata.go:73] "retrieving instance data from ec2 metadata"
metadata_ec2.go:29] "Retrieving EC2 instance identity Metadata" regionFromSession=""
metadata.go:82] "error retrieving instance data from ec2 metadata" err="could not get EC2 instance identity metadata: operation error ec2imds: GetInstanceIdentityDocument, canceled, context deadline exceeded"
metadata.go:85] "retrieving instance data from kubernetes api"
envvar.go:172] "Feature gate default state" feature="ClientsPreferCBOR" enabled=false
envvar.go:172] "Feature gate default state" feature="InformerResourceVersion" enabled=false
envvar.go:172] "Feature gate default state" feature="InOrderInformers" enabled=true
envvar.go:172] "Feature gate default state" feature="WatchListClient" enabled=false
envvar.go:172] "Feature gate default state" feature="ClientsAllowCBOR" enabled=false
metadata.go:90] "kubernetes api is available"
node.go:69] "regionFromSession Node service" region=""What happened?

What you expected to happen?
node.region to be available in the helm chart that set the AWS_REGION environment variable so node.go picks this up
https://github.com/kubernetes-sigs/aws-fsx-csi-driver/blob/master/pkg/driver/node.go#L64C23-L64C33

How to reproduce it (as minimally and precisely as possible)?
deploy the driver using helm with a serviceaccount enabled
controller:
region: eu-north-1
serviceAccount:
annotations:
eks.amazonaws.com/role-arn: arn:aws:iam::xxx:role/aws-fsx-driver-role

Anything else we need to know?:

Environment

  • Kubernetes version (use kubectl version):
  • Driver version:
@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label May 15, 2025
@coolstim coolstim linked a pull request May 15, 2025 that will close this issue
@coolstim
Copy link
Author

#430

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants