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
What happened:
The calico.yaml as referenced in the EKS documentation fails on Arm64 nodes, as the quay.io images are not multi-arch, and there is no logic to determine the underlying architecture in the yaml.
What you expected to happen:
The calico.yaml both in the repo and referenced in the docs would work on Arm64 nodes, now the EKS support for Graviton2 is GA, and calico itself works well on Arm64.
How to reproduce it (as minimally and precisely as possible):
Create EKS cluster, create an Arm64-based managed node group, attempt to deploy Calico via the documentation.
Anything else we need to know?:
Happy to help fix if you'd like, it should be pretty simple to add os/arch selectors.
If this is going to be a while to fix, if the docs could be updated in the meantime so as not to cause customer distress.
Also as the Stars Policy Demo is still not officially supported on Arm64, please update the docs to mention that, for customers who are following the docs with Arm64 clusters.
There was a previous here: #1047, however it only covered the preview (and the official docs haven't been updated post-EKS Graviton2 GA)
The text was updated successfully, but these errors were encountered:
We should consolidate this YAML or have one source of truth for generating the Calico YAML (and others for that matter) and push to Helm charts. There's an Helm chart with the same content here: https://github.com/aws/eks-charts/tree/master/stable/aws-calico. I will sync up @jaypipes on how we can to manage these and report back
What happened:
The calico.yaml as referenced in the EKS documentation fails on Arm64 nodes, as the quay.io images are not multi-arch, and there is no logic to determine the underlying architecture in the yaml.
What you expected to happen:
The calico.yaml both in the repo and referenced in the docs would work on Arm64 nodes, now the EKS support for Graviton2 is GA, and calico itself works well on Arm64.
How to reproduce it (as minimally and precisely as possible):
Create EKS cluster, create an Arm64-based managed node group, attempt to deploy Calico via the documentation.
Anything else we need to know?:
Happy to help fix if you'd like, it should be pretty simple to add os/arch selectors.
If this is going to be a while to fix, if the docs could be updated in the meantime so as not to cause customer distress.
Also as the Stars Policy Demo is still not officially supported on Arm64, please update the docs to mention that, for customers who are following the docs with Arm64 clusters.
There was a previous here: #1047, however it only covered the preview (and the official docs haven't been updated post-EKS Graviton2 GA)
The text was updated successfully, but these errors were encountered: