James Sturtevant
James Sturtevant
yes, opened https://github.com/kubernetes/test-infra/pull/33395 to enable it after this merges
I was able to reproduce this
reverting https://github.com/kubernetes/kubernetes/commit/4060ee60c1d2e5ba1fba1f8729adfc211cee1b6f fixes the issue
https://github.com/kubernetes/kubernetes/pull/127100
the bootstrapping extension looks like a red hearing. You could test it by starting a VM outside CAPZ manually: ``` az image create -n testvmimage -g cluster-api-images --os-type --source az...
/lgtm we have tests passing after these changes https://testgrid.k8s.io/sig-windows-master-release#capz-windows-2022-master-serial-slow with https://github.com/kubernetes-sigs/windows-testing/pull/459
@dante159753 I see we didn't document this in our docs for image builder but we have some docs over at cluster-api-azure that describe why you can't set a password: https://capz.sigs.k8s.io/topics/windows#vm-password-and-access...
/remove-lifecycle rotten @ritikaguptams I believe this is already applied in the sub. Can we make this ready to merge?
would this be appropriate for `wasm-tools`?
Now that we released wasmtime v22 support, we should have the right version but may need to expose some new apis