From e24f6b7a24cbdb4a160844b711cced5f5d49a565 Mon Sep 17 00:00:00 2001 From: Youhei Sakurai Date: Mon, 2 Jan 2023 23:48:48 +0900 Subject: [PATCH] Add missing required `type` field Although `LimitRange.spec.limits.type` was mandated in 2020, one LimitRange example still misses the field, so a validation error may confuse people referring. --- .../concepts/policy/limit-range/problematic-limit-range.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/content/zh-cn/examples/concepts/policy/limit-range/problematic-limit-range.yaml b/content/zh-cn/examples/concepts/policy/limit-range/problematic-limit-range.yaml index 74f22a06ceb..3b32c34f3a5 100644 --- a/content/zh-cn/examples/concepts/policy/limit-range/problematic-limit-range.yaml +++ b/content/zh-cn/examples/concepts/policy/limit-range/problematic-limit-range.yaml @@ -12,3 +12,4 @@ spec: cpu: "1" min: cpu: 100m + type: Container