You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/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?
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:
The text was updated successfully, but these errors were encountered:
/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
kubectl version
):The text was updated successfully, but these errors were encountered: