helm chart creation

[sebadob]

The goal is to finally create a Helm chart for Rauthy for a much easier deployment inside Kubernetes in the future.

This is a lot of work and will probably take some time and be done in between other things, when it makes sense.

[sebadob]

The Helm chart has been postponed for the moment until the config has been stabilized more towards v1.0.0.
I might maybe even build a Kubernetes operator directly which may be able to do auto-updates in the future.

[wt]

Would you be interested in a very basic helm chart that expects you to load a secret containing the config before you install the chart? I have one that I have been using for a few weeks to play with rauthy, and I would love to help you with this task.

[sebadob]

Yeah regarding this issue, I am not sure if a Helm chart is still the right approach, or if Kustomize would be better.

What I want to avoid, and what most Helm charts do very badly, is re-defining every config variable (even worse when location / names change) and then create the config from it. It's not only a huge maintenance overhead, but also very unnecessary. Just because you can do this, does not mean it's a good idea. So I guess the initial approach can be thrown away.

Having the config as a separate file makes the most sense, yes. Then you only need very few templating values for setting up the services and deployments. I think Kustomize would be a better fit for that and more straight forward.

But , if you have a working Helm chart though, yes sure go ahead and add it, then maybe in combination with a section in the book. The only important thing for me is, that you should be able to do everything with it and not just some "hello world" examples. And a single install / update of the helm chart should do the trick without the need to do any manual things beforehand. It should be easy and straight forward to use it.

---

Rauthy is reaching a point where it actually makes sense to take a 2nd look at this, because it's mostly feature complete and somewhat close to the first v1.0.0-rc I would say. I don't expect too many breaking config changes at this point, and when the config is separate (which is where Kustomize would come in handy), you don't even need to touch the other files and just provide a copy of the complete reference config, beaucse all documentation already exists for each value.