From 0245ad3aad96ee63be3502715b397c2e8bdae8d1 Mon Sep 17 00:00:00 2001 From: Roman Marusyk Date: Tue, 5 Jan 2021 20:57:13 +0200 Subject: [PATCH] Remove too old content --- .../admission-controllers.md | 19 +------------------ 1 file changed, 1 insertion(+), 18 deletions(-) diff --git a/content/en/docs/reference/access-authn-authz/admission-controllers.md b/content/en/docs/reference/access-authn-authz/admission-controllers.md index e57813ec12..8d01b1d20c 100644 --- a/content/en/docs/reference/access-authn-authz/admission-controllers.md +++ b/content/en/docs/reference/access-authn-authz/admission-controllers.md @@ -792,25 +792,8 @@ versions 1.9 and later). ## Is there a recommended set of admission controllers to use? -Yes. For Kubernetes version 1.10 and later, the recommended admission controllers are enabled by default (shown [here](/docs/reference/command-line-tools-reference/kube-apiserver/#options)), so you do not need to explicitly specify them. You can enable additional admission controllers beyond the default set using the `--enable-admission-plugins` flag (**order doesn't matter**). +Yes. The recommended admission controllers are enabled by default (shown [here](/docs/reference/command-line-tools-reference/kube-apiserver/#options)), so you do not need to explicitly specify them. You can enable additional admission controllers beyond the default set using the `--enable-admission-plugins` flag (**order doesn't matter**). {{< note >}} `--admission-control` was deprecated in 1.10 and replaced with `--enable-admission-plugins`. {{< /note >}} - -For Kubernetes 1.9 and earlier, we recommend running the following set of admission controllers using the `--admission-control` flag (**order matters**). - -* v1.9 - - ```shell - --admission-control=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota - ``` - - * It's worth reiterating that in 1.9, these happen in a mutating phase -and a validating phase, and that for example `ResourceQuota` runs in the validating -phase, and therefore is the last admission controller to run. -`MutatingAdmissionWebhook` appears before it in this list, because it runs -in the mutating phase. - - For earlier versions, there was no concept of validating versus mutating and the -admission controllers ran in the exact order specified.