clusterctl v1alpha3 should not install/manage v1alpha4 management cluster

[fabriziopandini]

User Story

As an operator, I would like clusterctl to have version checks in place so to prevent prevents potentially destructive operations due to version skew.

Detailed Description

Cluster API v1alpha4 is introducing changes in how providers are deployed (see e.g webhooks running with manager).

As a consequence, we should make sure that version checks are in place so to prevent prevents potentially destructive operations due to version skew. More specifically

• clusterctl version v1alpha3 should not be allowed to run on v1alpha4 clusters ⚠️ Clustectl v1alpha3 should block on v1alpha4 clusters #4265
• clusterctl version v1alpha3 should not be allowed to install v1alpha4 version of providers 🌱clusterctl v1alpha3 should not install v1alpha4 providers #4252
• clusterctl version v1alpha3 should not be allowed to upgrade management cluster with v1alpha4 version of providers ⚠️ Clusterctl v1alpha3 should not upgrade to v1alpha4 #4268

/kind feature

[fabriziopandini]

/milestone v0.3.x

/area clusterctl
/priority important-soon

/assing
/lifecycle active

[fabriziopandini]

PR merged
/close

[k8s-ci-robot]

@fabriziopandini: Closing this issue.

In response to this:

PR merged
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.