This was from last years conference, so the speakers don't always check on here, and they don't get notified of comments. Best bet is to track Nic down on LinkedIn to ask him the question directly.

If you install argo using helm chart, you can override them using values file. If installed manually, kustomization or want to override them in cluster, argocd-cm and argocd-cmd-params-cm configmaps.

Thanks @ssbostan. This is one of the best argocd videos I have watched on KZbin. 👏

I preferred rendered manifest model or rendered helm with kustomization. Check CNCF talks for more info about these patterns.

Watch this space. It will take a couple of weeks but I'll put together a public repo with the demo code

@@stephenjudd9799 did you managed to finished the demo code?

@@stephenjudd9799 did you managed to finish the demo code?

@@stephenjudd9799 Thanks!

@@stephenjudd9799 Did you managed to finish the demo code?

I don't know what you mean but based on the docs when using raw manifests with directory plugin, memory usage can be grown up to 300x of the on the rest size.

looks line an amazing idea wanna collab on it to produce together maybe?🤔🤔🤔🤔

Apologies for not answering sooner - I didn't realise there were any comments until today! It will take me a couple of weeks but I'll setup a public Github repo with the demo code (other people have asked also)

@@stephenjudd9799 Would be really helpful if we could have this code, it's really well explained :)

@@stephenjudd9799 did you have any updates about it? i really need this :(

@@stephenjudd9799 Any updates about this? i really need it :(

@@stephenjudd9799 did you managed to finish the code?

Amazing talk

Not clear to me as well. Instead of using terraform we need to install custom operator…. But how? With tf?

"The main idea behind having an operator is to have a system running constantly, looking for events to take action and maintain the desired state. For example, if the helmfile command executed by the terraform command fails, how can it be retried? Additionally, how can the argocd version be upgraded automatically? With an operator, these tasks can be easily automated."

My personal opinion is that using TF for deploying stuff into K8s clusters is an anti-pattern as you now have 2 sources of truth for the K8s cluster state: the K8s control plane and a tfstate file, so the chance of drift increases. I also don't much like the K8s related providers, i.e. the Helm, Helmfile and Kubernetes ones. I think the kubectl one is ok but it hasn't been touched for years. All that said, I did use TF to deploy my Helmfile operator into my K8s cluster (using raw manifests and the kubectl provider) as a 'one off', i.e. once the operator was installed I would never need to use TF to deploy anything else into the cluster.

Feel free to contact me , I have the end to end to solution with ESO and AWS SM although in the POC capacity and I am sure same is similar for Azure Vault