Incorrect priority value in dashboard

[jnoordsij]

Welcome!

• [X] Yes, I've searched similar issues on GitHub and didn't find any.
• [X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?

Assign manual router priority values to my cert-manager ingress routes and the web-to-443 redirect, with values near the maximum allowed value (MaxInt64). Then searched for the PRIORITY value within the dashboard (e.g. on /dashboard/#/http/routers/web-to-443%40internal).

Expected to see the value I assigned to this 9223372036854774805 (= MaxInt64 - 1002)

What did you see instead?

A slightly higher (rounded?) value: 9223372036854775000

This seems to be just a visual bug, as the cert-manager ingress route which I assigned a priority of 9223372036854774806 did actually get preferred after updating the values.

Note that I also saw some internal routes having priority 9223372036854776000 listed in the dashboard, which is over the possible limit, hence raising my suspicion of some sort of visual bug.

Further note: when inspecting backend requests, I noticed the following response body:

{
  "entryPoints": [
    "web"
  ],
  "middlewares": [
    "redirect-web-to-443@internal"
  ],
  "service": "noop@internal",
  "rule": "HostRegexp(`{host:.+}`)",
  "priority": 9223372036854775000,
  "status": "enabled",
  "using": [
    "web"
  ],
  "name": "web-to-443@internal",
  "provider": "internal"
}

So it looks like the "backend" is to blame here...?

What version of Traefik are you using?

v3.0.0-rc5

What is your environment & configuration?

Kubernetes (DOKS) + Traefik Helm chart

If applicable, please paste the log output in DEBUG level

No response