Skip to content
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

nodeSelector for targeting nodes on amd64 arch not arm64 for multi arch clusters #471

Closed
hugoprudente opened this issue Mar 23, 2020 · 2 comments

Comments

@hugoprudente
Copy link
Contributor

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

Pods

kube-system         ebs-csi-controller-74f94778d6-7wcx5                        2/2     Running             0          24s
kube-system         ebs-csi-controller-74f94778d6-8j79s                        0/2     CrashLoopBackOff             0          28s
kube-system         ebs-csi-node-2kd9x                                         3/3     Running             0          50s
kube-system         ebs-csi-node-9cvrp                                         3/3     Running             0          32s
kube-system         ebs-csi-node-lrwvp                                         0/3     CrashLoopBackOff   0          11s
kube-system         ebs-csi-node-pkjwd                                         3/3     Running             0          70s
k8s-ci-robot added a commit that referenced this issue Mar 28, 2020
Adding amd64 as nodeSelector to avoid arm64 archtectures (#471)
@leakingtapan
Copy link
Contributor

/close

@k8s-ci-robot
Copy link
Contributor

@leakingtapan: Closing this issue.

In response to this:

/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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants