/argocd-addons

Primary LanguageShell

Requirements

These are the dependencies required to be installed on the local machine.

  • docker desktop
  • kubectl cli
  • argocd cli
  • k3d cli

Architecture

For these exercises, we will deploy a control-plane architecture. This means that we will only have 1 ArgoCD instance stood up and it will managed multiple clusters. You can deploy each exercise in the same manner if using an ArgoCD instance for each cluster. The only difference would be that the destination can be set to in-cluster. In some examples, this actually could make deployment easier.

We will be deploying everything into one ArgoCD instance and then it will deploy the add-ons to the correct clusters. For this reason, it is best to go through the exercise as is and then you can experiment and add different clusters if you would like afterwards.

Introduction

Start DIND Container

To start, fork this repo and clone it to your computer. Open a terminal and make sure you cd to the cloned repo in the root directory. This will ensure that scripts gets attached and you can run the necassary commands.

To make the overall changes universal, I decided to have a docker container connect to the docker socket. This way we can run linux commands, even if you are running windows.

If you change the network, ensure that gets updated in the cluster_config.sh script.

docker network create argo-network
docker run --rm -it --privileged --network argo-network -v /var/run/docker.sock:/var/run/docker.sock -v $(pwd)/scripts:/scripts docker:latest sh -c "apk add bash && /bin/bash"

If using PowerShell:

docker network create argo-network
docker run --rm -it --privileged --network argo-network -v /var/run/docker.sock:/var/run/docker.sock -v ${pwd}/scripts:/scripts docker:latest sh -c "apk add bash && /bin/bash"

Running The Commands

In each section, there will be a script that will print the commands that should be run. I decided to do it this way as there is some back and forth between the localhost and the container. I tried to make it so that most of the commands are run inside the dind container and that way anyone can follow along, no matter the operating system of the localhost.

Also, by printing the commands needed, you can change the config to something you might like better and it should still work the same. You can add more clusters or remove whatever clusters you want.

Bootstrap ArgoCD Clusters

Within the dind container, run

/scripts/bootstrap-argocd-generator.sh

This will print all the commands needed to run and install the argocd clusters. You can copy all the commands and just run them or go through each section. This allows you to go at your own pace and be comfortable running the commands.

Open ArgoCD UI

Within the dind container, run

/scripts/argocd-ui-generator.sh

This will give the command to run the localhost machine. You will need to run the port forward command on the localhost and then you can open a web browser to see the ArgoCD UI. The username and password will be dumped to the terminal as well.

Cleanup ArgoCD Clusters

Within the dind container, run

/scripts/cleanup-clusters-generator.sh

This will cleanup all the k3d clusters. This should be run within the dind container.

Cleanup Localhost

Within the dind container, run

/scripts/cleanup-localhost-generator.sh

Copy this command and exit the dind container. You can then run those commands to remove and cleanup anything that was done from the local host and start from a clean slate.

Tutorial

Simple Apps

In this tutorial you will deploy simple ArgoCD applications. This is a very manual process and you will quickly see the disadvantages to using this method.

kubectl apply -f .\apps\argo-control-plane\ -f .\apps\argo-prod\ -f .\apps\argo-dev\

App of Apps

In this tutorial you will deploy the same applications as the simple applications, but we will do it a more gitops way. While this is a much better pattern, you will quickly see that this doesn't scale very well if you are dealing with more than a handful of clusters.

kubectl apply -f .\app-of-apps\argo-control-plane\bootstrap.yaml -f .\app-of-apps\argo-prod\bootstrap.yaml -f .\app-of-apps\argo-dev\bootstrap.yaml

AppSets

In this tutorial you will see how we can easily scale and some best practices so that you can effectively manage 100s of clusters. While there are still some ArgoCD limitations, this can scale very well from management perspective.

kubectl apply -f .\appsets

App of AppSets

In this tutorial we will fill in the missing piece to make using AppSets fulling gitops, but in a way that is still managable and without Kargo.

kubectl apply -f .\app-of-appsets\