You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We used traefik as the ingressroute in kubernetes, the backend HTTP service needs long time to handle the requests and it can cache the requests. On average, a request takes 30s to complete.
To control the rate limit, we configured the rateLimite middleware, like 10 req/s, and we send requests as 20 req/s.
What did you see instead?
We saw traefik not working as expected, it only limited several requests, not as the one we configured.
Does traefik have different behaviors for long latency vs. short latency requests. We also tried the short latency service, like the whoami, the rateLimit work as expected.
traefik.toml: | [metrics] [metrics.prometheus] entryPoint = "metrics" addEntryPointsLabels = true addServicesLabels = true buckets = [0.1, 0.3, 1.2, 5.0, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60] [accessLog] format = "json" [global] # prevent Traefik from checking newer versions in production checknewversion = false # prevent Traefik from collecting and sending stats from production sendanonymoususage = false [log] level = "INFO" format = "json" [api] dashboard = true insecure = true [providers] # Configuration reload frequency: # * duration that Traefik waits for, after a configuration reload, before taking into account any new configuration refresh event # * the most recent one is taken into account, and all the previous others are dropped. [providers.file] filename = "/config/traefik.toml" watch = true [providers.kubernetesCRD] throttleDuration = "10s" allowCrossNamespace = true [providers.kubernetesIngress] [entryPoints] [entryPoints.metrics] address = ":9100" [entryPoints.traefik] address = ":9000" [entryPoints.websecure] address = ":8443" [entryPoints.websecure.http.tls] [entryPoints.web] address = ":8000" [ping] entryPoint = "traefik" [tls] # without duplicating this cert config and with SNI enabled, Traefik won't # find the certificates for your host. It may be a Traefik's issue. [[tls.certificates]] certFile = "/mnt/secrets-store/tls.crt" keyFile = "/mnt/secrets-store/tls.key" stores = ["default"] [tls.stores] [tls.stores.default] [tls.stores.default.defaultCertificate] # without specifying in here your certs, Traefik will create its own # certificate certFile = "/mnt/secrets-store/tls.crt" keyFile = "/mnt/secrets-store/tls.key"
Add more configuration information here.
If applicable, please paste the log output in DEBUG level
No response
The text was updated successfully, but these errors were encountered:
Thanks for the feedback, I closed the issue accordingly.
@nmengin why did you close this? Is this a problem? Could you give solution to such long latency request rate limit? Or will you take it as a feature request? Thanks!
Welcome!
What did you do?
We used traefik as the ingressroute in kubernetes, the backend HTTP service needs long time to handle the requests and it can cache the requests. On average, a request takes 30s to complete.
To control the rate limit, we configured the rateLimite middleware, like 10 req/s, and we send requests as 20 req/s.
What did you see instead?
We saw traefik not working as expected, it only limited several requests, not as the one we configured.
Does traefik have different behaviors for long latency vs. short latency requests. We also tried the short latency service, like the whoami, the rateLimit work as expected.
What version of Traefik are you using?
0a79643
What is your environment & configuration?
Add more configuration information here.
If applicable, please paste the log output in DEBUG level
No response
The text was updated successfully, but these errors were encountered: