This repo serves as a companion to the talk at GitOpsCon 2021 "Managing multiple clusters with GitOps and ClusterAPI" organized by the CNCF GitOps Working Group, a pre-day event for KubeconEU 2021.
It leverages the new ApplicationSet controller for ArgoCD to scan a folder with cluster definitions and creates an Application per cluster, calling the chart in charts/azure-managed-cluster to deploy an AKS cluster with ClusterAPI for Azure controller.
- Fork this repo and
sedyour github username for mine:
sed -i 's/ams0/youruser/' root/clusters-appset.yaml- Install an AKS cluster with ArgoCD with ApplicationSet controller, ingress-nginx, cert-manager. The is the name before
.LOCATIOn.cloudapp.azure.com
cd 01-setup
./seed-setup.sh <URL> <LOCATION>- Install ClusterAPI with Azure provider (edit the script if you don't have the environment variables: AZURE_SUBSCRIPTION_ID, AZURE_TENANT_ID, AZURE_CLIENT_ID and AZURE_CLIENT_SECRET set to a service principal with enough rights to create AKS clusters in your subscription.)
./02-capz-setup.sh- Install the root app
./03-rootapp.shThe root app will pull the manifests from the root folder in your forked repo, applying the ApplicationSet ArgoCD which in turn will create clusters according to the manifests present in the clusters folder (create a subfolder per cluster, named after the desired cluster name).
- Once you have a workload cluster, login in ArgoCD and add the workload cluster:
argocd login $URL.$LOCATION.cloudapp.azure.com:443 --username admin --password supersecret --grpc-webGet the kubeconfig and add it to ArgoCD context
kubectl get secret -n clusters aks3-kubeconfig -o yaml -o jsonpath={.data.value} | base64 --decode | tee aks3.kubeconfig
argocd cluster add aks3 --name aks3 --kubeconfig aks3.kubeconfig
rm aks3.kubeconfigAn ApplicationSet is already in place on the management cluster to deploy ArgoCD Applications present in the workloads folder, and deploy them to the target cluster.