From f4dfc3f08419914df009016421862907b0896344 Mon Sep 17 00:00:00 2001 From: Qing Ju Date: Wed, 10 Jun 2020 16:57:11 -0700 Subject: [PATCH] Clarified LimitRange is enabled by default --- content/en/docs/concepts/policy/limit-range.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/content/en/docs/concepts/policy/limit-range.md b/content/en/docs/concepts/policy/limit-range.md index 8bea6c88e7..7c97af88ad 100644 --- a/content/en/docs/concepts/policy/limit-range.md +++ b/content/en/docs/concepts/policy/limit-range.md @@ -26,9 +26,7 @@ A _LimitRange_ provides constraints that can: ## Enabling LimitRange -LimitRange support is enabled by default for many Kubernetes distributions. It is -enabled when the apiserver `--enable-admission-plugins=` flag has `LimitRanger` admission controller as -one of its arguments. +LimitRange support has been enabled by default since Kubernetes 1.10. A LimitRange is enforced in a particular namespace when there is a LimitRange object in that namespace.