What keeps this repository from being "Production Ready"?

[benjigoldberg]

Hi team!

We're longtime users of the old chart and very excited to someday upgrade to 2.0. I've searched through the issues and a the pull requests to try and understand more about why the chart is labeled as not production ready. Is there any chance a contributor or maintainer could provide a little more insight into whats missing and what needs to be done?

We might be interested in participating in helping this along, as well.

[dtomcej]

Hello @benjigoldberg,

The migration from Traefik v1 to v2 shifts a lot of the configuration from traefik to the provider objects. The static configuration of entrypoints, redirects, TLS configuration etc, are all now dynamic, and are configurable through the providers.

For kubernetes, this means that the CRDs provide almost all of the configuration required to customize Traefik to run in kubernetes.

When we created this chart, we really were unsure how much configuration was going to be needed to be baked into the chart to provide functionality similar to the stable/traefik chart. For this reason, we made sure that it was listed as "in development here".

This chart was first published when Traefik 2.0.0 was the latest release. Although it was a stable release, we had too many unknowns at that point regarding this chart to confidently pursue this as a production ready chart at that point.

Lastly, being non-production ready meant that we could rapidly iterate, and would not have to deal with deprecation, backwards compatibility, and other behaviour that could become a real drag on the development process.

Realistically, there is nothing stopping you from using this chart in production now. The only thing to note is that we haven't frozen the configuration and customization to be backwards compatible, so new chart versions may not be compatible with older values.

I hope this gives the insight you were looking for.

[benjigoldberg]

@dtomcej thank you for taking the time to write this up -- this is very helpful. Looking forward to trying this out!