Red Hat OpenShift · Rate Limits
Red Hat Openshift Rate Limits
OpenShift's user-facing surfaces (Kubernetes API, oc CLI, console) inherit upstream Kubernetes APIServer flow control rather than enforcing a Red Hat-published rate ceiling. The managed cloud services (ROSA, ARO, OpenShift Dedicated, OpenShift on IBM Cloud) carry SLAs of 99.95–99.99% but no public per-second request ceiling.
Red Hat Openshift Rate Limits is the machine-readable rate-limit profile for Red Hat OpenShift on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 2 rate-limit definitions, measuring varies.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Kubernetes, Containers, Cloud, and Rate Limiting.
2 Limits
Throttle: 429
KubernetesContainersCloudRate Limiting
Limits
Kubernetes APIServer flow control account
governed by Kubernetes APIServer Priority and Fairness; no Red Hat-published ceiling
Managed-service SLA (ROSA / ARO / Dedicated / IBM) cluster
99.95-99.99% uptime SLA per managed service tier
Policies
APIServer Priority and Fairness
OpenShift inherits Kubernetes APF, which prioritizes essential controllers and throttles excessive client traffic with 429 responses; consumers should honor Retry-After and use informers/watch instead of polling.
SLA-backed Availability
Managed OpenShift services target 99.95-99.99% monthly uptime; cluster-control-plane throttling and resilience are managed by Red Hat / cloud provider, not the customer.