polinchw / cluster-addons

cluster-addons

Description

This repo contains a list of helm charts that will all be deployed to a cluster. It's deployed with an ArgoCD application-set that scans all the folders under the /addons director for charts.

Kustomize

• Place a values files that corresponds to the environment you want to deploy in such as values-dev.yaml in the directory that contains the helm chart.

• Create a Kustomize overlay that matches the name of the enviroment such as overlays/dev. Place a kustomization.yaml and application-set.yaml patch in the overlay/dev directory.

Deployment with Kustomize

Dev:

kubectl apply -k overlays/dev

Prod:

kubectl apply -k base

Rollback

It is recommended to make changes to the HEAD if you want to revert a change. If you do need to roll back to a previous commit you would change the ApplicationSet section.

apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
metadata:
  name: cluster-addons
  namespace: argocd
spec:
  generators:
  - git:
      repoURL: https://github.com/polinchw/cluster-addons.git
      revision: <previous-hash-or-tag-goes-here>
      directories:
      - path: addons/*

cluster-addons's Issues

question regarding addons

Hi!

First of all, thanks for the detailed writeup on autopilot and argo. I just had a question around the addons helm charts... What is the reasoning behind having the helm chart files in your repo, as opposed to just using the helm chart package and then using a kustomization to specify the version and your values file?

And secondly, does using the application set allow argo to track the changes for each of the applications (addons) where using an application directly wouldn't? I notice changing the application set itself doesn't trigger a sync without touching the application directory in the autopilot repo for the cluster addons, where as changes to the addons does.

Thanks again

Andy