You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Additionally, the Azure Cloud Provider will need to be installed on each downstream Cluster, for the nodes to be initialized correctly. +
97
-
+
98
-
We can do this automatically at Cluster creation using a https://cluster-api.sigs.k8s.io/tasks/experimental-features/cluster-resource-set[ClusterResourceSet]. +
99
-
Beware of the `azure-cloud-controller-manager` image version number on the ClusterResourceSet manifest. This is hardcoded, but should match the version of Kubernetes that the Cluster is using. +
101
+
* Additionally, the https://capz.sigs.k8s.io/self-managed/cloud-provider-config[Azure Cloud Provider] will need to be installed on each downstream Cluster, for the nodes to be initialized correctly. +
102
+
For this example we are also going to install https://docs.tigera.io/calico/latest/about/[Calico] as the default CNI. +
100
103
+
101
-
The ClusterResourceSet is configured to match any Cluster with the `cloud-provider: azure` label. +
104
+
We can do this automatically at Cluster creation using the https://rancher-sandbox.github.io/cluster-api-addon-provider-fleet/[Cluster API Add-on Provider Fleet]. +
105
+
This Add-on provider is installed by default with {product_name}. +
106
+
Two `HelmApps` need to be created first, to be applied on the new Cluster via label selectors. +
0 commit comments