Refer to/Include bindy helm charts

[Hobart2967]

Heya :)

I made helm charts for your awesome project, as I am currently trying it :)

https://github.com/[Hobart2967/bindy-charts](https://github.com/Hobart2967/bindy-charts)

Would be nice if you could refer to them or - even include them natively over here :)

[ebourgeois]

Hey @Hobart2967 , first off, thank you. Genuinely. Building charts for a project you're just picking up is a real act of generosity, and the fact that you took the time to package it up for others says a lot. I don't want any of what follows to land as dismissive of that effort.

That said, I'll be honest with you about a deliberate decision rather than leave you guessing: bindy ships raw manifests on purpose, and I don't plan to adopt or maintain a Helm chart in-tree.
This isn't an oversight or a "haven't gotten to it yet", it's a design stance. My experience is that templating non-trivial deployments tends to push complexity into a place where it's hard to reason about: the thing you actually apply to the cluster is the rendered output, but the thing you read, review, and debug is the template plus a values file plus whatever logic sits between them. For an operator like bindy, CRDs, RBAC, a controller with real blast radius, I'd rather the manifests be legible and auditable exactly as they're applied, with no rendering step between intent and result. That legibility matters more to me than the install ergonomics Helm buys.

So I'm going to keep the canonical install path as plain manifests (and Kustomize for those who want overlays without a templating engine).

None of that makes your work less valid for the people who do want a chart, though. If you'd like, I'm happy to add a short "Community / third-party" note in the README pointing to bindy-charts, clearly marked as community-maintained and not officially supported by me, so folks who prefer Helm can find it while understanding the support boundary. That way your effort reaches people without me taking on a maintenance promise I know I won't keep up.

Let me know if you're good with that, and thanks again for trying bindy and caring enough to contribute.

[Hobart2967]

Heya,

first of all, thanks for the quick reaction! Adding a backlink would be awesome, thanks! I fully understand your decision and would not question it.

And also thanks for the kudos, appreciate that!

I am currently thinking about rebuilding my server based on k8s. Currently I have a manual provisioning of most of the things, utilizing docker composes where I can. But there are lots of things that can be done with k8s, including setting up a DNS server - with bindy, as I have seen this one as the most complete bind9 operator so far!