carvel VS vendir

You should take a look at Carvel maybe something in it could match with your needs.

There's a third option that's quickly rising in popularity, which is Carvel, works great for smaller teams, and allows progressive adoption since it can start as CLI for newer teams learning about gitops concepts.

Huge fan of Carvel tools, it's a whole bunch of them that can help with a wide array of use cases, grab one or two of them for a given scenario, or adopt a bunch that string together to solve larger problems.

+1 been using ytt and kapp, the Carvel stuff in its entirety is a much better experience than helm (it can keep helm to help migration, or deal with the fact everyone still distributes in helm).

Creating Carvel Community which :

https://carvel.dev (and especially the [KAPP](https://carvel.dev/kapp/) piece) is a set of excellent tools to level up on Kubernetes.

Take a look at Kapp on https://carvel.dev/ for this, possibly.

There are some attempts to gradually find alternatives to Helm while remaining compatible with it. See https://carvel.dev/ for example.

There is a lot of innovation possible in this space.

Hopefully this post has helped you make install process smoother, smarter, and made you discover CARVEL tools.

i never found myself struggling with submodules, but at times i found myself just slightly annoyed (especially when having to remove/replace submodules), especially when they are used for simpler use cases.

i actually ended up creating https://carvel.dev/vendir/ for some of the overlapping use cases. aside from not being git specific (for source content or destination), its entirely transparent to consumers of the repo as they do not need to know how some subset of content is being managed. (i am of course a fan of committing vendored content into repos and ignore small price of increasing repo size).

👉The aim of this post is to document this to make things even easier with a tool called CARVEL vendir