nodepool/releasenotes/notes/kubernetes-default-limits-f4bcc430a6274043.yaml
Benjamin Schanzel d60a27a787
Default limits for k8s labels and quota support
This adds config options to enforce default resource (cpu,mem) limits on
k8s pod labels. With this, we can ensure all pod nodes have resource
information set on them. This allows to account for max-cores and
max-ram quotas for k8s pod nodes. Therefore also adding these config
options. Also tenant-quotas can then be considered for pod nodes.

Change-Id: Ida121c20b32828bba65a319318baef25b562aef2
2022-05-02 11:35:04 +02:00

22 lines
942 B
YAML

---
features:
- |
Config options for kubernetes providers were added to define default limits
for cpu and memory for pod-type labels.
* attr:`providers.[kubernetes].pools.default-label-cpu`
* attr:`providers.[kubernetes].pools.default-label-memory`
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
labels. It thereby enables to account for pool and tenant quotas in terms
of cpu and memory consumption. New config options for kubernetes pools
therefore also include
* attr:`providers.[kubernetes].pools.max-cores`
* attr:`providers.[kubernetes].pools.max-ram`
The exsisting tenant quota settings apply accordingly. Note that cpu and
memory quotas can still not be considered for labels that do not specify
any limits, i.e. neither a pool default, nor label specific limit is set.