Infrastructure Azure not compatible with 1.0

[dtzar]

What steps did you take and what happened:
clusterctl init --infrastructure azure

produced

Fetching providers
Error: current version of clusterctl is only compatible with v1beta1 providers, detected v1alpha4 for provider infrastructure-azure

What did you expect to happen:
It provisions the azure management cluster. Perhaps this just hasn't been released yet? I can't see anything stating it shouldn't be, unless I'm not looking in the right place.

Environment:

• Cluster-api version: 1.0.0
• Minikube/KIND version: local k8s docker for desktop
• Kubernetes version: (use kubectl version): 1.22.2
• OS (e.g. from /etc/os-release): wsl on Windows 11

/kind bug
/label /area/provider/azure

[k8s-ci-robot]

@dtzar: The label(s) /label /area/provider/azure cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda

In response to this:

What steps did you take and what happened:
clusterctl init --infrastructure azure

produced

Fetching providers
Error: current version of clusterctl is only compatible with v1beta1 providers, detected v1alpha4 for provider infrastructure-azure

What did you expect to happen:
It provisions the azure management cluster. Perhaps this just hasn't been released yet? I can't see anything stating it shouldn't be, unless I'm not looking in the right place.

Environment:

• Cluster-api version: 1.0.0
• Minikube/KIND version: local k8s docker for desktop
• Kubernetes version: (use kubectl version): 1.22.2
• OS (e.g. from /etc/os-release): wsl on Windows 11

/kind bug
/label /area/provider/azure

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.

[sbueringer]

Yes, CAPZ doesn't have a v1beta1 compatible release yet, but there is work ongoing. One issue where this can be tracked is: kubernetes-sigs/cluster-api-provider-azure#1722

Not sure if there are others (@CecileRobertMichon)

[dtzar]

Thanks for the info/link @sbueringer. Interesting enough, when I try either 0.4.4 or 0.4.3 I get a different error:

Error: this version of clusterctl could be used only with "v1alpha4" management clusters, "v1beta1" detected

Which version of clusterctl is actually supported for Azure?

[sbueringer]

Thanks for the info/link @sbueringer. Interesting enough, when I try either 0.4.4 or 0.4.3 I get a different error:

Error: this version of clusterctl could be used only with "v1alpha4" management clusters, "v1beta1" detected

Which version of clusterctl is actually supported for Azure?

clusterctl v0.4.x should work. Are you running it against a clean cluster? I think this issue can occur if there are already v1beta1 things (IIRC CRDs) in the cluster

[vincepri]

/triage support
/milestone Next

[k8s-ci-robot]

@vincepri: The label(s) triage/support cannot be applied, because the repository doesn't have them.

In response to this:

/triage support
/milestone Next

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.

[dtzar]

There is no management cluster present. I did install the docker version, but uninstalled it and can see no deplyoments/pods present... but AH hah re: your comment. It seems the delete doesn't clean up the CRDs. 😔

[dtzar]

Is there a recommendation for a good way to cleanup the CRDs?

Add a | kubectl delete ... on the end?

kg customresourcedefinitions | grep -e cluster.x-k8s.io
clusterclasses.cluster.x-k8s.io                              2021-10-20T04:20:52Z
clusterresourcesetbindings.addons.cluster.x-k8s.io           2021-10-20T04:20:52Z
clusterresourcesets.addons.cluster.x-k8s.io                  2021-10-20T04:20:52Z
clusters.cluster.x-k8s.io                                    2021-10-20T04:20:52Z
dockerclusters.infrastructure.cluster.x-k8s.io               2021-10-20T04:20:56Z
dockerclustertemplates.infrastructure.cluster.x-k8s.io       2021-10-20T04:20:57Z
dockermachinepools.infrastructure.cluster.x-k8s.io           2021-10-20T04:20:58Z
dockermachines.infrastructure.cluster.x-k8s.io               2021-10-20T04:20:58Z
dockermachinetemplates.infrastructure.cluster.x-k8s.io       2021-10-20T04:20:58Z
kubeadmconfigs.bootstrap.cluster.x-k8s.io                    2021-10-20T04:20:53Z
kubeadmconfigtemplates.bootstrap.cluster.x-k8s.io            2021-10-20T04:20:53Z
kubeadmcontrolplanes.controlplane.cluster.x-k8s.io           2021-10-20T04:20:54Z
kubeadmcontrolplanetemplates.controlplane.cluster.x-k8s.io   2021-10-20T04:20:54Z
machinedeployments.cluster.x-k8s.io                          2021-10-20T04:20:52Z
machinehealthchecks.cluster.x-k8s.io                         2021-10-20T04:20:52Z
machinepools.cluster.x-k8s.io                                2021-10-20T04:20:52Z
machines.cluster.x-k8s.io                                    2021-10-20T04:20:52Z
machinesets.cluster.x-k8s.io                                 2021-10-20T04:20:52Z
providers.clusterctl.cluster.x-k8s.io                        2021-10-20T04:20:29Z

[sbueringer]

@dtzar I'm usually using kubectl get crd | grep "cluster.x-k8s.io" | awk '{print $1}' | xargs -I {} kubectl delete crd {}. But I wouldn't call it a recommendation, especially as it deletes all resources of those CRDs.

[dtzar]

Thanks! That did the trick. So... perhaps a bug on the delete not cleaning up the CRDs? If this is by design, I'll just close this issue out. I would recommend the documentation get updated because by default it says to install 1.x which isn't supported or mentioned on those pages.

[sbueringer]

@dtzar clusterctl delete has a --include-crd flag, so yes, it's intentional.

[sbueringer]

The problem is that the infra provider documentation integrated in the core CAPI book is not always up-to-date, I agree.

[CecileRobertMichon]

we do have a warning in the quickstart about this https://cluster-api.sigs.k8s.io/user/quick-start.html#warning

[dtzar]

I saw this warning @CecileRobertMichon - but no way without digging around to find what provider version Azure supports. I (like I'm sure many folks) just assume the major version there is supported. I think if you merge my PR it will help.

Ideally IMO that warning would contain some lingo like - Please check the version of clusterctl your provider supports before download