Ashutosh Kumar
Ashutosh Kumar
@andyzhangx -- Yes that makes sense. I can do that in a next PR as looks like this is bit out of scope of the current PR. wdyt?
This PR intends to test for a special inflection version.
/test pull-cluster-api-provider-azure-e2e-workload-upgrade
/test pull-cluster-api-provider-azure-e2e-csi-migration
https://github.com/kubernetes/test-infra/pull/27261
/test pull-cluster-api-provider-azure-e2e-csi-migration
/retest pull-cluster-api-provider-azure-e2e-csi-migration
/test pull-cluster-api-provider-azure-e2e-csi-migration
I have been trying to validate this manually. Especially around kubernetes 1.22 --> 1.23 upgrade paths. The following in-tree components for azure are the points of attention : **AzureDiskCSI Driver**...
**Scenario3: Upgraded cluster from Kubernetes version 1.22 to 1.23 by enabling external cloud provider** - The upgrade failed. The new control plane machine did not pass the `perFlight` checks. Readiness...