specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Rook
providerId: rook
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: true
tags:
  - Rook
  - Ceph
  - Kubernetes
  - Open Source
  - Rate Limiting
description: >-
  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.
sources:
  - https://rook.io/docs/rook/latest/
  - https://github.com/rook/rook
responseCodes:
  throttled: 429
limits:
  - name: Kubernetes API server (Rook CRDs)
    scope: cluster
    metric: requests_per_second
    limit: cluster-administrator configured (kube-apiserver flow control)
    notes: >-
      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.
  - name: Ceph RGW (S3 endpoint)
    scope: ceph_user
    metric: requests_per_second
    limit: configured per ObjectStore / RGW user
    notes: >-
      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:
  - name: Kubernetes-Native Throttling
    description: >-
      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.
  - name: Ceph RGW Configuration
    description: >-
      Object-storage rate, quota, and throttling policy is set on the Ceph cluster (radosgw
      config and user quotas) rather than at the Rook layer.
  - name: Self-Hosted Operator
    description: >-
      Because Rook is self-hosted, there is no project-level SaaS quota or burst contract;
      operational limits are the operator's responsibility.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com