Argo implementation

[rzsita]

Hello,
I can see a flux implementation.
Are there plans for an Argo implementation as well?

Thanks

[netthier]

I'd also be interested in this.
If not a full controller, a kluctl Config Management Plugin would also work well.

[codablock]

I think about this topic from time to time and I'm unsure if this will ever be implemented in a proper and satisfying manner. Kluctl is quite different compared to other configuration management tools as it is not only responsible for the creation/management of manifests but also for the deployment of these.

Deployment is happening with quite a few Kluctl specific behaviours, for example waiting for barriers and readiness. Also, the way Kluctl performs conflict resolution would be incompatible in how other tools perform it.

Parts of this (barriers for example) could be mapped to ArgoCD features (sync waves), but it will never be fully compatible because Kluctl has to hand over the deployment to ArgoCD.

Regarding the Flux controller: It is not really a Flux controller anymore. It still has "flux" in the name, but only for historical reasons. I figured out pretty early that the Kluctl controller actually has no dependencies on the Flux ecosystem and thus should live on its own. A future version, most likely when I introduce v1beta1 as API version, will also get a rename/move of the project.

My priority and long-term plan at the moment is to to provide a Kluctl specific UI solution. With this, Kluctl will be able to position itself as a full-blown GitOps alternative to ArgoCD and Flux. I hope I can give more details on this in the next weeks.

[netthier]

Regarding the Flux controller: It is not really a Flux controller anymore. It still has "flux" in the name, but only for historical reasons. I figured out pretty early that the Kluctl controller actually has no dependencies on the Flux ecosystem and thus should live on its own. A future version, most likely when I introduce v1beta1 as API version, will also get a rename/move of the project.

Does this mean it could also be already used in a cluster using ArgoCD? It'd be interesting to be able to deploy ApplicationSets of KluctlDeployments.

[codablock]

Does this mean it could also be already used in a cluster using ArgoCD? It'd be interesting to be able to deploy ApplicationSets of KluctlDeployments.

Yes this can be done. The Kluctl controller doesn't care about how the KluctlDeployment objects got deployed.

However, if ApplicationSets is the only reason why you want to use ArgoCD, then maybe look into https://kluctl.io/blog/2022/12/28/template-controller/. The template-controller solves the problem as the ApplicationSet, but in a generalised way.