public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 20:48:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

[2.14] Upstream Kubernetes ResourceQuota types support (#2263)

Browse Source 
* Update Resource Quota Type Reference page for support of all upstream Kubernetes ResourceQuota types

* Apply changes to v2.14 / zh files

* Apply suggestions from code review

Co-authored-by: Billy Tat <btat@suse.com>

* Apply feedback to other versions/zh, reword/reorder intro

* Add back zh content

---------

Co-authored-by: Billy Tat <btat@suse.com>
This commit is contained in:
Lucas Saintarbor
2026-03-24 10:27:52 -07:00
committed by GitHub
co-authored by Billy Tat
parent 85a32cd276
commit 7e0ceeffd5
4 changed files with 62 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/resource-quota-types.md
+22 -3
View File
@@ -2,13 +2,19 @@
title: 资源配额类型参考
---
创建资源配额相当于配置项目可用的资源池。你可以为以下资源类型设置资源配额：
When you create a resource quota, you are configuring the pool of resources available to the project. Rancher supports the use of arbitrary resource references and their quotas. This allows you to utilize all upstream [Kubernetes `ResourceQuota`](https://kubernetes.io/docs/concepts/policy/resource-quotas/#types-of-resource-quota) types when managing project resource quotas.
You can set resource limits for the following predefined resource types, where the `Custom` type enables specification of arbitrary resources and their quotas.
:::note
Support for arbitrary resource references using the `Custom` type does not cover resources in the `ext.cattle.io` API group.
:::
| 资源类型 | 描述 |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| CPU 限制\* | 分配给项目/命名空间的最大 CPU 量（以[毫核](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/#meaning-of-cpu)为单位）<sup>1</sup> |
| CPU 预留\* | 预留给项目/命名空间的最小 CPU 量（以毫核为单位）<sup>1</sup> |
| 内存限制\* | 分配给项目/命名空间的最大内存量（以字节为单位）<sup>1</sup> |
| 内存限制\* | 分配给项目/命名空间的最大内存量（[以字节为单位](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#meaning-of-memory)）<sup>1</sup> |
| 内存预留\* | 预留给项目/命名空间的最小内存量（以字节为单位）<sup>1</sup> |
| 存储预留 | 预留给项目/命名空间的最小存储量（以千兆字节为单位） |
| 服务负载均衡器 | 项目/命名空间中可以存在的负载均衡器服务的最大数量 |
@@ -19,9 +25,22 @@ title: 资源配额类型参考
| 持久卷声明 | 项目/命名空间中可以存在的持久卷声明的最大数量 |
| ReplicationController | 项目/命名空间中可以存在的最大 ReplicationController 数量 |
| 密文 | 项目/命名空间中可以存在的最大密文数量 |
| Custom\*\* | The specification of arbitrary resources and their quotas, beyond the resource types built into projects, as listed above. |
:::note **<sup>*</sup>**
在设置资源配额时，如果你在项目或命名空间上设置了任何与 CPU 或内存相关的内容（即限制或预留），所有容器都需要在创建期间设置各自的 CPU 或内存字段。你可以同时设置容器的默认资源限制，以避免为每个工作负载显式设置这些限制。详情请参阅 [Kubernetes 文档](https://kubernetes.io/docs/concepts/policy/resource-quotas/#requests-vs-limits)。
:::
:::
:::note **<sup>\*\*</sup>**
For example:
- `requests.nvidia.com/gpu: 4`
- `gold.storageclass.storage.k8s.io/requests.storage: 500Gi`
- `count/podtemplates: 10`
See the [Kubernetes documentation](https://kubernetes.io/docs/concepts/policy/resource-quotas/#quota-for-extended-resources) for many more examples.
:::