Tekton Rate Limits
Tekton itself does not enforce HTTP rate limits — its primary API is the Kubernetes API server, which applies its own request-rate limits (max-requests-inflight, max-mutating-requests-inflight, APF — API Priority and Fairness). Tekton controllers expose tunable knobs for concurrent reconciles, throttling outbound calls to the Kubernetes API, and the EventListener Sink. Tekton Triggers EventListeners are protected only by their own ingress / reverse-proxy configuration. Operators are responsible for placing rate limits at the cluster ingress, the EventListener service, and the Tekton Hub front-end if exposed publicly.
Tekton Rate Limits is the machine-readable rate-limit profile for Tekton on the APIs.io network, in the API Commons Rate Limits shape.
It captures 5 rate-limit definitions, measuring kube-api-requests-per-second, kube-api-burst, pipelineruns, webhooks-per-second, and requests-per-priority-level.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 4 backoff/retry policies defined and response codes documented for unauthenticated, forbidden, and tooManyRequests.
Tagged areas include DevOps, CI/CD, Kubernetes, Open Source, and Rate Limiting.
generated, dated 2026-05-08.
Limits
Policies
Sources
- https://tekton.dev/docs/pipelines/install/
- https://tekton.dev/docs/triggers/eventlisteners/
- https://kubernetes.io/docs/concepts/cluster-administration/flow-control/
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.