Container Registry
Container Registry
Container Registry
Document
Container Registry (CR)
What's new
Overview
Billing
Billing item
Getting started
User guide
User authorization
Authorization management
Robot account management
Instance management
Namespace management
OCI artifact repository management
OCI artifact management
Version management
Tag immutability rule management
Tag retention rules management
Access configuration
Access control
Distribution acceleration
P2P acceleration
Image lazy loading
Registry replication
Audit log management
Alerts and notifications
Best practices
Image push and pull
Image migration and synchronization
DevOps delivery
FAQ
Authorization
VPC
Image push and pull
Limits
Registry replication
P2P acceleration
Access control
API
Calling Method
Instance Management
Namespace Management
OCI Artifact Repository Management
OCI Artifact Version Management
Domain Management
Access Endpoint Management
Temporary Access Key
Robot Account Management
General Data Structure
Artifact repository AR
What's new
Product overview
Getting started
User guide
Instance management
Repository Management
Access control
Permanent access credentials
Temporary access credentials
Maven package management
Generic package management
PyPI package management
NPM package management
Uploading packages
Downloading packages
AI package management
Permission management
API Reference
Repository Management
Package management
Version Management
File Management
Temporary Key Management
General Data Structure
- Documentation
Container RegistryContainer Registry (CR)FAQLimitsHow do I handle the "pull QPS exceeded" error after a pod starts?
Copy page
Download PDFLimits
How do I handle the "pull QPS exceeded" error after a pod starts?
Copy pageDownload PDFHow do I handle the "pull QPS exceeded" error after a pod starts?
Issue description
After a pod starts, images fail to be pulled with the error pull QPS exceeded. A sample log is shown below.
1s Normal Created pod/****-pod Created container step-git-clone-0
1s Normal Started pod/****-pod Started container step-git-clone-0
1s Normal Pulling pod/****-pod Pulling image "cr-cn-****.volces.com/cp-system/exec-bash:v1.0.0"
1s Normal PullImageFailed taskrun/**** build step "step-tos-cache-2-push" is pending with reason "pull QPS exceeded"
Solution
This issue is caused by limits in the Kubelet add-on itself, not by CR. If this issue occurs, increase the values of registryBurst and registryPullQPS in Kubelet. The final parameter values depend on your specific workload scenario. Tune them based on your actual business needs.
Last updated: 2026.10.19 15:46:50
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
