adeploy VS helm-x

We created adeploy, which is using Jinja Templating to render Manifests out of a set of template files and variables. We added some functions i.e. to set versions, create labels, include files or to handle secret creation using gopass and support to run in CI/CD without re-creating secrets. Source + (some) docs: https://github.com/awesome-it/adeploy

We wrote adeploy which brings Jinja templating for both vanilla manifests and Helm Charts which includes a bench of useful Jinja templating functions i.e. for labeling, secret management etc... The tool supports multiple deployments at different namespaces/releases with different Jinja variables and also includes support to deploy secrets directly from GoPass. It can also be used in CI/CD while secrets are not re-deployed when running via CI/CD. The tool still lacks of some detailed docs and a public pip repo, but this is wip.

Exactly this. No need to wrap your app that only you consume and deploy as a helm chart. If you want to benefit from Helms application management features like rollbacks, you can use helm-x or helmify

TLDR Use cdk8s + helm-x to be able to deploy cdk8s manifests as helm charts, with all the benifits of helm.

We are already very close to that IMHO. The functionality is not yet built in Helm. If you look at CDK8s + Helm X you can already do it for your team. The only limitation is that you can't publish that as a chart.

helm-x - Treat any Kustomization or K8s manifests directory as a Helm chart