whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Integrate flags into "Transport security" section

Browse Source
This commit is contained in:
Nils Hanke
2022-07-09 04:55:43 -07:00
parent c5d8916092
commit 959cb92224
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/security/controlling-access.md
+3 -2
View File
@@ -22,10 +22,11 @@ following diagram:
## Transport security ## Transport security
In a typical Kubernetes cluster, the API serves on port 443, protected by TLS. By default, the Kubernetes API server listens on port 6443 on the first non-localhost network interface, protected by TLS. In a typical production Kubernetes cluster, the API serves on port 443. The port can be changed with the `--secure-port`, and the listening IP address with the `--bind-address` flag.
The API server presents a certificate. This certificate may be signed using The API server presents a certificate. This certificate may be signed using
a private certificate authority (CA), or based on a public key infrastructure linked a private certificate authority (CA), or based on a public key infrastructure linked
to a generally recognized CA. to a generally recognized CA. The certificate and corresponding private key can be set by using the `--tls-cert-file` and `--tls-private-key-file` flags.
If your cluster uses a private certificate authority, you need a copy of that CA If your cluster uses a private certificate authority, you need a copy of that CA
certificate configured into your `~/.kube/config` on the client, so that you can certificate configured into your `~/.kube/config` on the client, so that you can