argo-helm VS cdk8s

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.

Have you looked into https://cdk8s.io/? I've been using it for a while now, and I must admit TypeSript does help a lot. Not really sold on your React syntax yet, but well done nevertheless

I, personally, prefer to wrap it in CDKTF/CDK8S in golang and manage with Crossplane Composition Functions, but your mileage may vary. I'm finding way too bugs in CDK's... but it calms me a bit, that Amazon folks actually looking into it.

What about https://cdk8s.io/?

I'm interested cdk8s but haven't tried it yet: https://github.com/cdk8s-team/cdk8s

Always love seeing someone else create a similar solution as your own (albiet likely better!).

I have the same setup with K3S running on a couple PIs. You have a nice CI but I decided to use cdk8s[1] which lets you compile Typescript into K8 files. For access I did almost exactly the same but with CloudFlare Tunnels (might look into Tailscale). Stealing the zigbee2mqtt and room assistant ideas.

Where do you store volumes? I eventually just bought a NAS and mount persistent NFS volumes off it.

1. https://cdk8s.io/

All AWS resources as well as kubernetes manifest and kubernetes AddOns are managed and installed using CDK (AWS Cloud Development Kit) and CDK8S (Cloud Development Kit for Kubernetes)

Assuming either JS or Python is acceptable, is recommend you check out cdk8s. Allows you to compose manifests, but in a "boring" language without a new collection of issues.

In this blog, it provides the way to create Kyverno policy as code using CDK8S typescript.

CDK8s