From 8312e0917d8e47524f0bc8d1bab7fbadb334616d Mon Sep 17 00:00:00 2001 From: Youhei Sakurai Date: Mon, 2 Jan 2023 13:21:31 +0900 Subject: [PATCH] [en] Add missing required `type` field to LimitRange example (#38706) * Add missing required `type` field to examples Although `LimitRange.spec.limits.type` was mandated in 2020, a few LimitRange examples still miss the field, so they may confuse people referring. * 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/en/examples/concepts/policy/limit-range/problematic-limit-range.yaml b/content/en/examples/concepts/policy/limit-range/problematic-limit-range.yaml index 5fbfe632c0..ee89cb79fa 100644 --- a/content/en/examples/concepts/policy/limit-range/problematic-limit-range.yaml +++ b/content/en/examples/concepts/policy/limit-range/problematic-limit-range.yaml @@ -12,3 +12,4 @@ spec: cpu: "1" min: cpu: 100m + type: Container