zuul/nodepool
Code Issues Proposed changes

Fix typo in release notes

Browse Source 
Change-Id: Ie8f44e361507eda67ea739e51a65507860e36002
This commit is contained in:
James E. Blair 2022-06-17 10:55:13 -07:00
parent 1b1eab77b0
commit b2d4e3c356
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
releasenotes/notes/kubernetes-default-limits-f4bcc430a6274043.yaml
View File

@ -4,8 +4,8 @@ features:
Config options for kubernetes providers were added to define default limits Config options for kubernetes providers were added to define default limits
for cpu and memory for pod-type labels. for cpu and memory for pod-type labels.
* attr:`providers.[kubernetes].pools.default-label-cpu` * :attr:`providers.[kubernetes].pools.default-label-cpu`
* attr:`providers.[kubernetes].pools.default-label-memory` * :attr:`providers.[kubernetes].pools.default-label-memory`
These values will apply to all pod-type labels within the same pool that do These values will apply to all pod-type labels within the same pool that do
not override these limits. This allows to enforce resource limits on pod not override these limits. This allows to enforce resource limits on pod
@ -13,8 +13,8 @@ features:
of cpu and memory consumption. New config options for kubernetes pools of cpu and memory consumption. New config options for kubernetes pools
therefore also include therefore also include
* attr:`providers.[kubernetes].pools.max-cores` * :attr:`providers.[kubernetes].pools.max-cores`
* attr:`providers.[kubernetes].pools.max-ram` * :attr:`providers.[kubernetes].pools.max-ram`
The exsisting tenant quota settings apply accordingly. Note that cpu and The exsisting tenant quota settings apply accordingly. Note that cpu and
memory quotas can still not be considered for labels that do not specify memory quotas can still not be considered for labels that do not specify