-
Notifications
You must be signed in to change notification settings - Fork 812
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
Deploy arm64 nodepool on the GKE Build Cluster #7123
Conversation
/lgtm In case, other folx want to shime in. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: upodroid The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This has been deployed. Need another lgtm |
/lgtm |
/hold cancel |
/cc @ameukam @BenTheElder
According to the docs, arm64 nodepools are automatically tainted by GCP to block amd64 workloads running on there. Jobs have to either use nodeselectors or taint the pod to tolerate arm64 nodes if the image is multiarchitecture.
https://cloud.google.com/kubernetes-engine/docs/how-to/prepare-arm-workloads-for-deployment#overview
Fixes: