Does Traefik’s sticky‑session middleware support session tracking for non‑frontend providers?

Goal: Verify whether Traefik’s sticky‑session middleware can track sessions when using providers other than the built‑in frontend provider, and understand any associated memory‑usage behavior.

Constraints: The middleware documentation states it is only available with the frontend provider; it is unclear if other providers expose a comparable session‑tracking mechanism or if the middleware falls back to a no‑op, potentially leaving stale entries in the in‑memory cache.

• Does the sticky‑session middleware create and maintain session entries when Traefik is configured with a provider such as Docker, Kubernetes, or Consul?
• If session tracking is unavailable for non‑frontend providers, what configuration or alternative approach should be used to avoid unbounded growth of the in‑memory session cache?