From 8155f1d16da72cadc2ea4702e9203788cb40d8a4 Mon Sep 17 00:00:00 2001 From: Siman <42727060+simanw@users.noreply.github.com> Date: Wed, 8 Sep 2021 19:30:10 -0700 Subject: [PATCH] Update controlling-access.md as --insecure-port flag deprecated (#29447) * Update English version of controlling-access.md as --insecure-port flag deprecated * Update controlling-access.md as --insecure-port flag deprecated * Update content/en/docs/concepts/security/controlling-access.md Co-authored-by: Qiming Teng Co-authored-by: Qiming Teng --- content/en/docs/concepts/security/controlling-access.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/security/controlling-access.md b/content/en/docs/concepts/security/controlling-access.md index 9d6c2b9617e..1a0c93d8cfe 100644 --- a/content/en/docs/concepts/security/controlling-access.md +++ b/content/en/docs/concepts/security/controlling-access.md @@ -142,7 +142,7 @@ By default, the Kubernetes API server serves HTTP on 2 ports: - is intended for testing and bootstrap, and for other components of the master node (scheduler, controller-manager) to talk to the API - no TLS - - default is port 8080, change with `--insecure-port` flag. + - default is port 8080 - default IP is localhost, change with `--insecure-bind-address` flag. - request **bypasses** authentication and authorization modules. - request handled by admission control module(s).