You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Well... My PR for this was pulled into ArgoCD v3.0.0, so in that regard, yes. However, I later learned that KCL itself can read/write anywhere via file in the stdlib, so trying to come up with a multi-tenant solution was sort of a pointless exercise.
thanks @MacroPower, just curious — are you still using KCL in your work or maybe as a hobby? I noticed that KCL development has been slower lately compared to 2024, so I was wondering how things are going on your end.
thanks @MacroPower, just curious — are you still using KCL in your work or maybe as a hobby? I noticed that KCL development has been slower lately compared to 2024, so I was wondering how things are going on your end.
Just as a hobby. I would not personally use any of these DSLs at work (learned my lesson after hepito was killed by vmware and a ton of jsonnet tooling was unmaintained for years). I did have high hopes for KCL since it was accepted by CNCF so it is a bit sad to see it go the same way as so many other projects in this category. I do plan to keep using it though, I think, as it mostly has all of the features I would want. And at some point it might be a good reason to learn Rust...
I have high hopes too. I’ve been considering using KCL at my company as an alternative to Helm templating—it feels much cleaner and more maintainable. At some point, I’ll probably need to learn Rust as well, especially since so much of the tooling is built around it, @MacroPower
@daudcanugerah@MacroPower what is your impresion now, as almost a year has passed? Do you think KCL is still to be considered? It looks like development has slowed down but I would like to try an approach like this (and not jsonnet again). Thoughts?
@alexmeise KCL covers most of my configuration requirements, but the current Language Server (LSP) experience is not reliable enough for real development workflows. In addition, KCL lacks a first-class workspace concept similar to Go’s go.work, which makes managing multi-module or multi-package projects difficult.
@alexmeise I moved my entire homelab to KCL. In general I've arrived at the same consensus as @daudcanugerah -- though for just me I ended up with a fairly reasonable and scalable approach I think.
Activity
MacroPower commentedon Dec 25, 2024
Depends on argoproj/argo-cd#15186
daudcanugerah commentedon Jun 11, 2025
so is it safe then?
MacroPower commentedon Jun 12, 2025
Well... My PR for this was pulled into ArgoCD v3.0.0, so in that regard, yes. However, I later learned that KCL itself can read/write anywhere via file in the stdlib, so trying to come up with a multi-tenant solution was sort of a pointless exercise.
daudcanugerah commentedon Jun 16, 2025
thanks @MacroPower, just curious — are you still using KCL in your work or maybe as a hobby? I noticed that KCL development has been slower lately compared to 2024, so I was wondering how things are going on your end.
MacroPower commentedon Jun 20, 2025
Just as a hobby. I would not personally use any of these DSLs at work (learned my lesson after hepito was killed by vmware and a ton of jsonnet tooling was unmaintained for years). I did have high hopes for KCL since it was accepted by CNCF so it is a bit sad to see it go the same way as so many other projects in this category. I do plan to keep using it though, I think, as it mostly has all of the features I would want. And at some point it might be a good reason to learn Rust...
daudcanugerah commentedon Jun 23, 2025
I have high hopes too. I’ve been considering using KCL at my company as an alternative to Helm templating—it feels much cleaner and more maintainable. At some point, I’ll probably need to learn Rust as well, especially since so much of the tooling is built around it, @MacroPower
alexmeise commentedon Apr 14, 2026
@daudcanugerah @MacroPower what is your impresion now, as almost a year has passed? Do you think KCL is still to be considered? It looks like development has slowed down but I would like to try an approach like this (and not jsonnet again). Thoughts?
daudcanugerah commentedon Apr 14, 2026
@alexmeise KCL covers most of my configuration requirements, but the current Language Server (LSP) experience is not reliable enough for real development workflows. In addition, KCL lacks a first-class workspace concept similar to Go’s go.work, which makes managing multi-module or multi-package projects difficult.
MacroPower commentedon Apr 17, 2026
@alexmeise I moved my entire homelab to KCL. In general I've arrived at the same consensus as @daudcanugerah -- though for just me I ended up with a fairly reasonable and scalable approach I think.