Skip to content

Commit c5d8916

Browse files
authored
Remove section about the removed localhost port
1 parent b861992 commit c5d8916

File tree

1 file changed

+0
-28
lines changed

1 file changed

+0
-28
lines changed

content/en/docs/concepts/security/controlling-access.md

Lines changed: 0 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -136,34 +136,6 @@ The cluster audits the activities generated by users, by applications that use t
136136

137137
For more information, see [Auditing](/docs/tasks/debug/debug-cluster/audit/).
138138

139-
## API server ports and IPs
140-
141-
The previous discussion applies to requests sent to the secure port of the API server
142-
(the typical case). The API server can actually serve on 2 ports:
143-
144-
By default, the Kubernetes API server serves HTTP on 2 ports:
145-
146-
1. `localhost` port:
147-
148-
- is intended for testing and bootstrap, and for other components of the master node
149-
(scheduler, controller-manager) to talk to the API
150-
- no TLS
151-
- default is port 8080
152-
- default IP is localhost, change with `--insecure-bind-address` flag.
153-
- request **bypasses** authentication and authorization modules.
154-
- request handled by admission control module(s).
155-
- protected by need to have host access
156-
157-
2. “Secure port”:
158-
159-
- use whenever possible
160-
- uses TLS. Set cert with `--tls-cert-file` and key with `--tls-private-key-file` flag.
161-
- default is port 6443, change with `--secure-port` flag.
162-
- default IP is first non-localhost network interface, change with `--bind-address` flag.
163-
- request handled by authentication and authorization modules.
164-
- request handled by admission control module(s).
165-
- authentication and authorization modules run.
166-
167139
## {{% heading "whatsnext" %}}
168140

169141
Read more documentation on authentication, authorization and API access control:

0 commit comments

Comments
 (0)