Andy Zhang
cc @lzhecheng
/assing @lzhecheng
/assign @lzhecheng
and make sure the CSI drivers could be disabled by switch in cluster creation, we want to install latest versions(or even master branch) of CSI driver in some testing scenario.
cc @CecileRobertMichon @marosset this is the reason why CSI driver does not work on Windows node now.
> Ref: https://github.com/kubernetes-sigs/image-builder/pull/690/files#diff-adaa5bbfc20ce5e21aed6ea1e95dfca1d060eb4cf11622555d5242007ec02798R33 > > All traffic on port 80 is blocked. hostNetwork-enabled containers are _still_ be able to reach wireserver. > > Why does CSI driver need access to...
and when I start a driver pod, it cannot access api-server using kubeconfig on the windows node, error is like following: ``` 2022-03-08T04:29:27.4405461Z stderr F I0308 04:29:27.439569 3996 azure.go:71] reading...
/ok-to-test
/ok-to-test
Looks like that's a node name issue (regression?) let me rerun those failed tests. ``` Sep 14 03:26:54.472: INFO: At 2022-09-14 03:11:53 +0000 UTC - event for azuredisk-volume-tester-bczvd: {attachdetach-controller }...