-
Notifications
You must be signed in to change notification settings - Fork 430
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2495 from CecileRobertMichon/calico-helm
Use Helm to install Calico CNI in e2e tests instead of ClusterResourceSets
- Loading branch information
Showing
96 changed files
with
1,683 additions
and
78,154 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,161 @@ | ||
| # CNI | ||
|
|
||
| By default, the CNI plugin is not installed for self-managed clusters, so you have to [install your own](https://cluster-api.sigs.k8s.io/user/quick-start.html#deploy-a-cni-solution). | ||
|
|
||
| Some of the instructions below use [Helm](https://helm.sh) to install the addons. If you're not familiar with using Helm to manage Kubernetes applications as packages, there's lots of good [Helm documentation on the official website](https://helm.sh/docs/). You can install Helm by following the [official instructions](https://helm.sh/docs/intro/install/). | ||
|
|
||
| ## Calico | ||
|
|
||
| To install [Calico](https://www.tigera.io/project-calico/) on a self-managed cluster using the office Calico Helm chart, run the commands corresponding to the cluster network configuration: | ||
|
|
||
| ### For IPv4 clusters | ||
|
|
||
| ```bash | ||
| IPV4_CIDR_BLOCK=<cluster ipv4 pod cidr block> \ | ||
| helm repo add projectcalico https://projectcalico.docs.tigera.io/charts && \ | ||
| helm install calico projectcalico/tigera-operator -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-azure/main/templates/addons/calico/values.yaml --set-string installation.calicoNetwork.ipPools[0].cidr="$IPV4_CIDR_BLOCK" --namespace tigera-operator --create-namespace | ||
| kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-azure/main/templates/addons/calico/felix-override.yaml | ||
| ``` | ||
|
|
||
| ### For IPv6 clusters | ||
|
|
||
| ```bash | ||
| IPV6_CIDR_BLOCK=<cluster ipv6 pod cidr block> \ | ||
| helm repo add projectcalico https://projectcalico.docs.tigera.io/charts && \ | ||
| helm install calico projectcalico/tigera-operator -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-azure/main/templates/addons/calico-ipv6/values.yaml --set-string installation.calicoNetwork.ipPools[0].cidr="$IPV6_CIDR_BLOCK" --namespace tigera-operator --create-namespace | ||
| kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-azure/main/templates/addons/calico/felix-override.yaml | ||
| ``` | ||
|
|
||
| ### For dual-stack (IPv4 + IPv6) clusters | ||
|
|
||
| ```bash | ||
| IPV4_CIDR_BLOCK=<cluster ipv4 pod cidr block> \ | ||
| IPV6_CIDR_BLOCK=<cluster ipv6 pod cidr block> \ | ||
| helm repo add projectcalico https://projectcalico.docs.tigera.io/charts && \ | ||
| helm install calico projectcalico/tigera-operator -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-azure/main/templates/addons/calico-dual-stack/values.yaml --set-string installation.calicoNetwork.ipPools[0].cidr="$IPV4_CIDR_BLOCK",installation.calicoNetwork.ipPools[1].cidr="$IPV6_CIDR_BLOCK" --namespace tigera-operator --create-namespace | ||
| kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-azure/main/templates/addons/calico/felix-override.yaml | ||
| ``` | ||
|
|
||
| <aside class="note"> | ||
|
|
||
| <h1> Note </h1> | ||
|
|
||
| For Windows nodes, you also need to copy the kubeadm-config configmap to the calico-system namespace so the calico-node-windows Daemonset can find it: | ||
|
|
||
| ```bash | ||
| kubectl create ns calico-system | ||
| kubectl get configmap kubeadm-config --namespace=kube-system -o yaml \ | ||
| | sed 's/namespace: kube-system/namespace: calico-system/' \ | ||
| | kubectl create -f - | ||
| ``` | ||
|
|
||
| </aside> | ||
|
|
||
|
|
||
| For more information, see the [official Calico documentation](https://projectcalico.docs.tigera.io/getting-started/kubernetes/helm). | ||
|
|
||
| ## Flannel | ||
|
|
||
| This section describes how to use [Flannel](https://github.com/flannel-io/flannel) as your CNI solution. | ||
|
|
||
| ### Modify the Cluster resources | ||
|
|
||
| Before deploying the cluster, change the `KubeadmControlPlane` value at `spec.kubeadmConfigSpec.clusterConfiguration.controllerManager.extraArgs.allocate-node-cidrs` to `"true"` | ||
|
|
||
| ```yaml | ||
| apiVersion: controlplane.cluster.x-k8s.io/v1beta1 | ||
| kind: KubeadmControlPlane | ||
| spec: | ||
| kubeadmConfigSpec: | ||
| clusterConfiguration: | ||
| controllerManager: | ||
| extraArgs: | ||
| allocate-node-cidrs: "true" | ||
| ``` | ||
| #### Modify Flannel config | ||
| _NOTE_: This is based off of the instructions at: https://github.com/flannel-io/flannel#deploying-flannel-manually | ||
| You need to make an adjustment to the default flannel configuration so that the CIDR inside your CAPZ cluster matches the Flannel Network CIDR. | ||
| View your capi-cluster.yaml and make note of the Cluster Network CIDR Block. For example: | ||
| ```yaml | ||
| apiVersion: cluster.x-k8s.io/v1beta1 | ||
| kind: Cluster | ||
| spec: | ||
| clusterNetwork: | ||
| pods: | ||
| cidrBlocks: | ||
| - 192.168.0.0/16 | ||
| ``` | ||
| Download the file at `https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml` and modify the `kube-flannel-cfg` ConfigMap. | ||
| Set the value at `data.net-conf.json.Network` value to match your Cluster Network CIDR Block. | ||
|
|
||
| ```bash | ||
| wget https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml | ||
| ``` | ||
|
|
||
| Edit kube-flannel.yml and change this section so that the Network section matches your Cluster CIDR | ||
|
|
||
| ```yaml | ||
| kind: ConfigMap | ||
| apiVersion: v1 | ||
| metadata: | ||
| name: kube-flannel-cfg | ||
| data: | ||
| net-conf.json: | | ||
| { | ||
| "Network": "192.168.0.0/16", | ||
| "Backend": { | ||
| "Type": "vxlan" | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| Apply kube-flannel.yml | ||
|
|
||
| ```bash | ||
| kubectl apply -f kube-flannel.yml | ||
| ``` | ||
|
|
||
| # External Cloud Provider | ||
|
|
||
| To deploy a cluster using [external cloud provider](https://github.com/kubernetes-sigs/cloud-provider-azure), create a cluster configuration with the [external cloud provider template](https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-azure/main/templates/cluster-template-external-cloud-provider.yaml). | ||
|
|
||
| After the cluster has provisioned, install the `cloud-provider-azure` components using the official helm chart: | ||
|
|
||
| ```bash | ||
| helm install --repo https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/helm/repo cloud-provider-azure --generate-name --set infra.clusterName=${CLUSTER_NAME} | ||
| ``` | ||
|
|
||
| The Helm chart will pick the right version of `cloud-controller-manager` and `cloud-node-manager` to work with the version of Kubernetes your cluster is running. | ||
|
|
||
| After running `helm install`, you should eventually see a set of pods like these in a `Running` state: | ||
|
|
||
| ```bash | ||
| kube-system cloud-controller-manager 1/1 Running 0 41s | ||
| kube-system cloud-node-manager-5pklx 1/1 Running 0 26s | ||
| kube-system cloud-node-manager-hbbqt 1/1 Running 0 30s | ||
| kube-system cloud-node-manager-mfsdg 1/1 Running 0 39s | ||
| kube-system cloud-node-manager-qrz74 1/1 Running 0 24s | ||
| ``` | ||
|
|
||
| For more information see the official [`cloud-provider-azure` helm chart documentation](https://github.com/kubernetes-sigs/cloud-provider-azure/tree/master/helm/cloud-provider-azure). | ||
|
|
||
| ## Storage Drivers | ||
|
|
||
| ### Azure File CSI Driver | ||
|
|
||
| To install the Azure File CSI driver please refer to the [installation guide](https://github.com/kubernetes-sigs/azurefile-csi-driver/blob/master/docs/install-azurefile-csi-driver.md) | ||
|
|
||
| Repository: https://github.com/kubernetes-sigs/azurefile-csi-driver | ||
|
|
||
| ### Azure Disk CSI Driver | ||
|
|
||
| To install the Azure Disk CSI driver please refer to the [installation guide](https://github.com/kubernetes-sigs/azuredisk-csi-driver/blob/master/docs/install-azuredisk-csi-driver.md) | ||
|
|
||
| Repository: https://github.com/kubernetes-sigs/azuredisk-csi-driver |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.