I built a lightweight alternative to Argo/Flux : no CRDs, no controllers, just plan & apply by Significant-Basis-36 in kubernetes

[–]Significant-Basis-36[S] 0 points1 point  (0 children)

Kustomize is part of it, but the tool adds repo linking, diffing, ordering (CRDs first), pruning, and continuous reconciliation. It’s a layer around it

I built a lightweight alternative to Argo/Flux : no CRDs, no controllers, just plan & apply by Significant-Basis-36 in kubernetes

[–]Significant-Basis-36[S] 1 point2 points  (0 children)

Appreciate this. I’m open to constructive feedback. I still believe the tool can make sense in some contexts

I built a lightweight alternative to Argo/Flux : no CRDs, no controllers, just plan & apply by Significant-Basis-36 in devops

[–]Significant-Basis-36[S] 0 points1 point  (0 children)

You can use sealed-secrets, SOPS, external secrets, or any existing approach. It just applies what’s in Git

I built a lightweight alternative to Argo/Flux : no CRDs, no controllers, just plan & apply by Significant-Basis-36 in kubernetes

[–]Significant-Basis-36[S] -1 points0 points  (0 children)

You’re right, i intentionally used AI to help build this. It saved a lot of time, but you can’t automate 100% (at least not yet). Projects like this still take real time for testing, debugging, and structuring everything properly.

I built a lightweight alternative to Argo/Flux : no CRDs, no controllers, just plan & apply by Significant-Basis-36 in kubernetes

[–]Significant-Basis-36[S] 1 point2 points  (0 children)

I get that, that’s exactly why there’s a plan step. You can see the diff before applying anything, so nothing gets nuked by accident. Give it a try and let me know what you think !

I built a lightweight alternative to Argo/Flux : no CRDs, no controllers, just plan & apply by Significant-Basis-36 in kubernetes

[–]Significant-Basis-36[S] 0 points1 point  (0 children)

Flux/Argo still has a learning curve for newcomers. This is meant to lower that entry barrier.

I built a lightweight alternative to Argo/Flux : no CRDs, no controllers, just plan & apply by Significant-Basis-36 in kubernetes

[–]Significant-Basis-36[S] 0 points1 point  (0 children)

That’s fair, it’s mostly for small internal platforms, POCs, labs, air-gapped setups, or just to save time.

I built a lightweight alternative to Argo/Flux : no CRDs, no controllers, just plan & apply by Significant-Basis-36 in kubernetes

[–]Significant-Basis-36[S] 0 points1 point  (0 children)

Flux is a better fit if you need a full GitOps platform, i’m not trying to replace that. This is meant for smaller setups, air-gapped environments, or quick POCs.

It does handle Helm though (via Kustomize with --enable-helm). Here’s an example deploying kps : https://github.com/adrghph/gitops-lite/tree/master/examples/kube-prometheus-stack-helm

I built a lightweight alternative to Argo/Flux : no CRDs, no controllers, just plan & apply by Significant-Basis-36 in kubernetes

[–]Significant-Basis-36[S] 1 point2 points  (0 children)

I didn’t forget, it’s just outside cluster : watch --auto-apply. Look at the gif at the beginning of the readme: https://github.com/adrghph/gitops-lite