Rook · Rate Limits

Rook Rate Limits

Rook does not operate a hosted API and therefore does not impose project-level rate limits. The Rook CRDs are consumed via the Kubernetes API server in the operator's host cluster; any throttling is whatever the cluster administrator configures on the Kubernetes API server (kube-apiserver flow-control / API priority and fairness, --max-requests-inflight, client-go QPS/burst). The S3-compatible object endpoint that Rook can deploy on top of Ceph (via the RGW) is rate-limited by Ceph RGW configuration, not by Rook itself.

Rook Rate Limits is the machine-readable rate-limit profile for Rook on the APIs.io network, in the API Commons Rate Limits shape.

It captures 2 rate-limit definitions, measuring requests_per_second.

An exhausted limit returns HTTP 429.

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 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Rook, Ceph, Kubernetes, Open Source, and Rate Limiting.

2 Limits Exhausted: HTTP 429
Method: generated, dated 2026-05-05.
Written by API Evangelist on 2026-05-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
RookCephKubernetesOpen SourceRate Limiting

Limits

Kubernetes API server (Rook CRDs) cluster
requests_per_second
cluster-administrator configured (kube-apiserver flow control)
Rook CRDs (CephCluster, CephBlockPool, ObjectStore, etc.) are served by the host cluster's kube-apiserver. Throughput follows whatever Priority and Fairness configuration the cluster operator has set.
Ceph RGW (S3 endpoint) ceph_user
requests_per_second
configured per ObjectStore / RGW user
When Rook deploys an Object Store (RGW), per-user and per-bucket throttling is controlled by Ceph RGW configuration (rgw_max_concurrent_requests, user/bucket quotas), not by Rook.

Policies

Kubernetes-Native Throttling
All Rook control-plane traffic flows through the Kubernetes API server; clients should respect kube-apiserver 429 responses with Retry-After and configure client-go QPS and burst appropriately.
Ceph RGW Configuration
Object-storage rate, quota, and throttling policy is set on the Ceph cluster (radosgw config and user quotas) rather than at the Rook layer.
Self-Hosted Operator
Because Rook is self-hosted, there is no project-level SaaS quota or burst contract; operational limits are the operator's responsibility.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/rook-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.