From b2d4e3c356dcbbe61fa0807fe27d60580cf8b552 Mon Sep 17 00:00:00 2001 From: "James E. Blair" Date: Fri, 17 Jun 2022 10:55:13 -0700 Subject: [PATCH] Fix typo in release notes Change-Id: Ie8f44e361507eda67ea739e51a65507860e36002 --- .../notes/kubernetes-default-limits-f4bcc430a6274043.yaml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/releasenotes/notes/kubernetes-default-limits-f4bcc430a6274043.yaml b/releasenotes/notes/kubernetes-default-limits-f4bcc430a6274043.yaml index d7ff3f8f6..60cb4abc7 100644 --- a/releasenotes/notes/kubernetes-default-limits-f4bcc430a6274043.yaml +++ b/releasenotes/notes/kubernetes-default-limits-f4bcc430a6274043.yaml @@ -4,8 +4,8 @@ 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` + * :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 @@ -13,8 +13,8 @@ features: 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` + * :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