From 87d36ecfe14c7e7fdba4306ef9cc31a051deb0e4 Mon Sep 17 00:00:00 2001
From: Paulo Gomes <pjbgf@linux.com>
Date: Wed, 9 Sep 2020 09:48:47 +0100
Subject: [PATCH] Fix incorrect guidance on enabling EventRateLimit
---
.../docs/reference/access-authn-authz/admission-controllers.md | 2 --
1 file changed, 2 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 fda7119caf..0684ae22b7 100644
--- a/content/en/docs/reference/access-authn-authz/admission-controllers.md
+++ b/content/en/docs/reference/access-authn-authz/admission-controllers.md
@@ -202,8 +202,6 @@ is recommended instead.
This admission controller mitigates the problem where the API server gets flooded by
event requests. The cluster admin can specify event rate limits by:
- * Ensuring that `eventratelimit.admission.k8s.io/v1alpha1=true` is included in the
- `--runtime-config` flag for the API server;
* Enabling the `EventRateLimit` admission controller;
* Referencing an `EventRateLimit` configuration file from the file provided to the API
server's command line flag `--admission-control-config-file`: