Openshift Rate Limits
OpenShift inherits Kubernetes API Priority and Fairness (APF) flow control on the cluster kube-apiserver. The hosted Red Hat services (Cluster Manager / OCM API) enforce account-scoped throttling but do not publish numeric per-second limits; clients should honor 429 + Retry-After. Concurrent operations on the same resource use optimistic concurrency (resourceVersion); conflict surfaces as HTTP 409.
Openshift Rate Limits is the machine-readable rate-limit profile for OpenShift on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring varies and requests_per_second.
The profile also includes 4 backoff/retry policies defined and response codes documented for throttled, conflict, and unavailable.
Tagged areas include Containers, Kubernetes, and Rate Limiting.
Limits
Policies
Sources
- https://kubernetes.io/docs/concepts/cluster-administration/flow-control/
- https://docs.openshift.com/
- https://api.openshift.com/
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.