Make controller upgrade tests independent of minikube and kind
Closed this issue · 2 comments
Xenwar commented
As we have them, the upgrade of controlplane-components (CAPI, CAPM3...) uses kind cluster. The CI environment could have minikube or kind.
Regardless of the environment, the tests should run with the right KUBECONFIG.
ToDo:
For existing controlplane-components tests, remove the dependency on Kind cluster
- Verify that the tests run and succeed on both Minikube and Kind clusters
Xenwar commented
Note: CRDs are not replaced.
We cannot use the same cluster to successive upgrades of different component.
Therefore:
- use the same cluster when doing a one shot upgrades
Xenwar commented
This issue is outdated and no longer needed.