Thomas Boerger

Maybe it should be better to check for host and as a fallback check the for header. The traefik change have been integrated within the last release?

I'm using traefik already quite long and it always worked fine for me in combination with this middleware

There is an pass host Header Option I'm using with traefik

I will prepare a docker-compose scenario to see the exact behavior

There is also no automated upgrade path, currently you will loose the secrets and the entire build logs, even with the migration tool.

It depends on how we define it... We could also say that v1 is the default value and changes require the version attribute.

That could happen before 1.0.0, but with 1.0.0 there is a promise to avoid breaking changes. Breaking changes MUST result in a new schema versioning now.

But so far it's not required because there are no other versions :)

Are you sure about that? Not sure if I tested parameters, but I'm pretty sure the promote/rollback was only working like I built it.

The Screenshots are really looking awesome