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
Is your feature request related to a problem?/Why is this needed
When deploying the CSI Driver on a Multi Architecture node x86_64 and ARM64 the deployment and daemonSet does not support ARM64 and deploy the pods causing CrashLoopBackOff.
/feature
Describe the solution you'd like in detail
As multi node architectures can be recurrent, adding nodeSelector specific would resolve this issue.
Describe alternatives you've considered
I have considered using affinity, but node selector will be clean as discussing with the aws-fsx-csi-driver team, that I patched too.
Additional context
Nodes
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
ip-10-0-29-162.eu-west-1.compute.internal Ready <none> 2d22h v1.15.10-eks-bac369 10.0.29.162 <none> Amazon Linux 2 4.14.171-136.231.amzn2.x86_64 docker://18.9.9
ip-10-0-49-41.eu-west-1.compute.internal Ready <none> 24h v1.15.10-eks-bac369 10.0.49.41 <none> Amazon Linux 2 4.14.171-136.231.amzn2.aarch64 docker://18.9.9
ip-10-0-87-226.eu-west-1.compute.internal Ready <none> 24h v1.15.10-eks-bac369 10.0.87.226 <none> Amazon Linux 2 4.14.171-136.231.amzn2.aarch64 docker://18.9.9
ip-10-0-93-165.eu-west-1.compute.internal Ready <none> 2d22h v1.15.10-eks-bac369 10.0.93.165 <none> Amazon Linux 2 4.14.171-136.231.amzn2.x86_64 docker://18.9.9
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.
Is your feature request related to a problem?/Why is this needed
When deploying the CSI Driver on a Multi Architecture node x86_64 and ARM64 the deployment and daemonSet does not support ARM64 and deploy the pods causing CrashLoopBackOff.
/feature
Describe the solution you'd like in detail
As multi node architectures can be recurrent, adding nodeSelector specific would resolve this issue.
Describe alternatives you've considered
I have considered using affinity, but node selector will be clean as discussing with the aws-fsx-csi-driver team, that I patched too.
Additional context
Nodes
Pods
The text was updated successfully, but these errors were encountered: