argo-helm VS charts

I think your example with the ArgoCD Helm chart says it all. It can get incredibly complicated, and I had tremendous trouble getting it working, it broke all the time, getting the indentation right was a nightmare ... very unpleasant experience. I mean look at that chart, the authors have to constantly specify the indentation level everywhere.

plugin: name: argocd-vault-helm env: - name: release_name value: argocd - name: chart_name value: argo-cd - name: chart_repo value: https://argoproj.github.io/argo-helm - name: chart_version value: 5.17.1 - name: chart_values value: -f applicationset.yaml -f configs.yaml -f controller.yaml -f dex.yaml -f redis.yaml -f reposerver.yaml -f server.yaml -f notifications.yaml - name: args value: --include-crds

Another folder I want to discuss shortly is the Terraform folder. This project was installed by terraform basically but it can deployed easily with simple helm installation of ArgoCD . In the next attachment we can see the relevant values neccesary to apply our ArgoCD system : values-override.tpl

Finally, we have to install ArgoCD from the official Helm Chart but with extra configuration that provides modifications required to install Vault plugin via sidecar container.

# once againe make sure to use proper namespace kubens toolbox # install ArgoCD with provided vaules helm repo add argo https://argoproj.github.io/argo-helm helm install argocd argo/argo-cd -n toolbox -f argocd-helm-values.yaml

I'll give an example. Argo CD provides an example Application CR that has every field listed. It is clear and it is human-readable. The Application CRD is a bulky 2200-line file.

argocd_helm_config = { create_namespace = true name = "argo-cd" chart = "argo-cd" repository = "https://argoproj.github.io/argo-helm" namespace = "argocd" timeout = "3600" values = [templatefile("files/argocd-values.yaml", {})] }

```bash helm repo add argo https://argoproj.github.io/argo-helm

resource "helm_release" "argocd" { name = "argocd" repository = "https://argoproj.github.io/argo-helm" chart = "argo-cd" namespace = "argocd" version = "4.9.7" create_namespace = true values = [ file("argocd/application.yaml") ] }

New releases are available in the Argo CD repo and have been coordinated with the community Helm charts.

Typically, our IAM service is a third-party like keycloak or fusionauth which we can easily deploy on Kubernetes by means of a helm chart. Helm is a very practical package manager for Kubernetes. For example, a typical fusionauth deployment would look like something along these lines: