See the video here
Workloads are deployed through ArgoCD in an app-of-apps style deployment.
Configuration of the application is done via the bootstrap
root app that has it's own configuration within values.yaml
. This is propagated into the child apps.
When looking at the wider business context, we see how the applications in this repository can feed more broadly back into the business.
This folder contains application templates. You can either add a helm chart or git repository as the source. You can copy an existing application or import some you've written before for argocd.
Application | Link |
---|---|
Cats | https://github.com/AlexsJones/cats |
Cert manager | https://charts.jetstack.io |
Komodor | https://github.com/komodorio/helm-charts |
Observability CRDS | https://github.com/prometheus-community/helm-charts.git |
Local path provisioner | https://github.com/rancher/local-path-provisioner.git |
Logging | https://grafana.github.io/helm-charts |
Metallb | https://metallb.github.io/metallb |
Observability | https://prometheus-community.github.io/helm-charts |
Nginx | https://helm.nginx.com/stable |
Trivy | https://aquasecurity.github.io/helm-charts/ |
-
Spin up a Kubernetes cluster on your favourite cloud provider or hardware
-
Setup argocd
kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
- Save the Argocd password
kubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath="{.data.password}" | base64 -d
- Add this repository as a bootstrap cluster
kubectl apply -f bootstrap.yaml
Check values.yaml
and adjust as required
Prometheus CRD's when used with ArgoCD apply can get big, so here is a hack to get arond the sync errors Thanks to this guide.
- kubectl
- kubectx
- k9s
- jq
- kustomize
- helm
- sshuttle