Andy Zhang
cc @mboersma @jackfrancis
how can I create a hyper v2 node pool in capz? current error is `The selected VM size 'Standard_D2pls_v5' cannot boot Hypervisor Generation '1'` https://[storage.googleapis.com/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_blob-csi-driver/1634/pull-blob-csi-driver-e2e-arm64/1845733738135162880/artifacts/clusters/bootstrap/controllers/capz-controller-manager/capz-controller-manager-856c6d4446-g97zc/manager.log](https://storage.googleapis.com/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_blob-csi-driver/1634/pull-blob-csi-driver-e2e-arm64/1845733738135162880/artifacts/clusters/bootstrap/controllers/capz-controller-manager/capz-controller-manager-856c6d4446-g97zc/manager.log)
how can I set gen2 in test-infra config?
@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....
@Vegoo89 thanks for reporting this issue. May I know why do you want to use open source blob csi driver instead of managed one?
@jack4it are you using the open source csi driver following this guide? https://github.com/kubernetes-sigs/azurefile-csi-driver/blob/master/docs/workload-identity-deploy-csi-driver.md
/ok-to-test