mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-07 00:48:01 +01:00
22 lines
1.1 KiB
Plaintext
22 lines
1.1 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * microshift_configurig/microshift_tls-config.adoc
|
|
|
|
:_mod-docs-content-type: CONCEPT
|
|
[id="microshift-tls-config-con_{context}"]
|
|
= Using TLS with {microshift-short}
|
|
|
|
Transport layer security (TLS) profiles provide a way for servers to regulate which ciphers a client can use when connecting to the server. Using TLS helps to ensure that {microshift-short} applications use cryptographic libraries that do not allow known insecure protocols, ciphers, or algorithms. You can use either the TLS 1.2 or TLS 1.3 security profiles with {microshift-short}.
|
|
|
|
{microshift-short} API server cipher suites apply automatically to the following internal control plane components:
|
|
|
|
* API server
|
|
* Kubelet
|
|
* Kube controller manager
|
|
* Kube scheduler
|
|
* etcd
|
|
* Route controller manager
|
|
|
|
The API server uses the configured minimum TLS version and the associated cipher suites. If you leave the cipher suites parameter empty, the defaults for the configured minimum version are used automatically.
|
|
|
|
include::snippets/microshift-tls-ciphers.adoc[leveloffset=+2] |