-
Notifications
You must be signed in to change notification settings - Fork 427
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
support arm64 vm sku #5176
Comments
how can I create a hyper v2 node pool in capz? current error is |
cluster-api-provider-azure/templates/test/ci/cluster-template-prow-ci-version.yaml Line 243 in 76a735b
|
how can I set gen2 in test-infra config? |
See also kubernetes-sigs/image-builder#936
We haven't published gen2 images (or arm64 images) to the Marketplace, so you'd have to build and host the right images somewhere. Note that CAPZ is transitioning to a community gallery and won't be updating the Marketplace images from here on out. See #5167. |
@mboersma then what about Azure Linux node, does capz supports today? |
We have built Azure Linux 2 images, and I tried to make them the default in #4832, but I ran into a problem that I failed to figure out. (Help is welcome!) I intend to build Azure Linux 3 images for the community gallery when #5167 merges, but I don't know if they will pass tests until we figure out what isn't working. |
@mboersma I think if you could provide a parameter for Azure Linux 2 image in test-infra, that would be great, it's not necessary to set as default since the default setting change may break external users. |
/kind feature
Describe the solution you'd like
[A clear and concise description of what you want to happen.]
Currently when I create an arm64 vm sku node pool, e.g.
Standard_D2pls_v5
, it would failhttps://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_blob-csi-driver/1634/pull-blob-csi-driver-e2e-arm64/1845733738135162880
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: