Volcano · Rate Limits

Volcano Rate Limits

Volcano does not expose a vendor-side request-rate limit. As a Kubernetes-native scheduler running in the customer's cluster, "limits" in Volcano are workload-level resource quotas - CPU, memory, GPU, and queue capacity - enforced via the Queue CRD and standard Kubernetes ResourceQuota objects. Consumers of the Volcano API interact with the Kubernetes API server, whose rate-limit and admission-controller behavior governs request throttling.

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

It captures 2 rate-limit definitions, measuring varies.

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.

Tagged areas include Open Source, Kubernetes, Rate Limiting, and Quotas.

2 Limits
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
Open SourceKubernetesRate LimitingQuotas

Limits

Kubernetes API Server (cluster-side) cluster
varies
see kube-apiserver --max-requests-inflight / --max-mutating-requests-inflight
Volcano is consumed via the Kubernetes API; rate enforcement is whatever the cluster's API server is configured with.
Volcano Queue Capacity queue
varies
see Queue CRD spec.capability
Multi-dimensional resource cap (CPU, Memory, GPU) per Queue; enforced by Volcano scheduler, not as a request-rate limit.

Policies

Kubernetes-Native Throttling
All client interaction is via kubectl / client-go against the Kubernetes API server. Use the standard client-go QPS / burst tunables and respect 429 responses from the API server.
Queue-Based Fairness
Volcano enforces fairness through Queues with hierarchical resource inheritance, weight, and capability caps rather than per-second request limits.
Gang Scheduling Admission
Jobs are admitted only when the full PodGroup can be scheduled atomically; partial submissions are gated by the scheduler rather than throttled at the API surface.

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/volcano-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.