Should I Use Kluctl to Hydrate Manifests Before Deploying with ArgoCD?

0
11
Asked By CuriousCoder42 On

I'm relatively new to Kubernetes and trying to get my head around the deployment processes. Currently, we're using Helm charts with Helmsman in our lower environments. I stumbled upon Kluctl and really like its templating and project structure, plus it supports GitOps, which is a big plus for me. However, I've learned that our IDP team is planning on using ArgoCD, which has a different templating structure compared to both Helmsman and Kluctl. I'm curious if it's a valid strategy to use Kluctl to generate or "hydrate" the manifests while the IDP team uses ArgoCD for GitOps deployments of these pre-rendered manifests. What do you think?

2 Answers

Answered By DevGuru77 On

From what I gather, you want Kluctl to generate templates that are version-controlled via GitOps, which ArgoCD can then use, right? Just so you know, the flow is actually ArgoCD pulling the latest templates from Git and then using Kluctl as a plugin for its workflow. So you'll need to set up variables correctly for Kluctl to work in that environment. Sounds like a great integration!

CuriousCoder42 -

Exactly, that’s what I'm aiming for! But I’m wondering if this setup is actually a good practice.

Answered By TechSage99 On

It sounds like you're at a crossroads with the tools you want to use and the ones your IDP team prefers. Have you guys had a conversation about what exactly your needs are? Sometimes focusing on the actual challenges can yield better solutions than just pushing for a specific tool. Keep the conversation open!

CuriousCoder42 -

We are discussing. But when they say things like 'we've already decided on using x...' it gets tough for me to push back without being well-prepared.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.