Romain

Hello @jilleJr, > Our possible workarounds are either: > - Update app-root to respond 404 on /api/ endpoints > - Update our system test to ensure the /api/ healthcheck polling...

Hello @qmloong, Thanks for your contribution! At first glance, we think that the index shouldn't be leveraged to introduce entropy in server selection. We would prefer to insert a server...

> In this way, the user experience is not very good for a large number of traefik to do forward proxy clusters...Especially automated configuration or deployment for traefik. The server...

> For instance, we use traefik as the forward proxy for kubelet (1 : 1) as local proxy to access to 3 kube-apiserver instance A, B, C If my cluster...

Hello @schewara, Thanks for your interest in Traefik! This is the expected behavior as, for now, there is nothing in place to remove the outdated data of that metric in...

Hello @EmiiKhaos @m-wynn, We are still open to hear your ideas on implementing this feature in Traefik !

Hello @jerrywoo96, Thanks for your interest in Traefik! We labeled this issue as "proposal", which means that it needs to be refined before any implementation. While the use case is...

Hello @jerrywoo96, Thanks for implementing a new plugin! Can we consider that this issue can be closed and addressed by this new plugin?

Thanks for reporting that @danepowell. @jerrywoo96 We made a proposal to fix the issue, PTAL: https://github.com/jerrywoo96/AddMissingHeaders/pull/1

Hello @jerrywoo96, > Is this fixed in traefik 2.8.4? Websocket connection still failed. It is fixed in v2.8.5: https://github.com/traefik/traefik/releases/tag/v2.8.5.