From c1c44ef47b9e05148ea77114657bd9b0b3cd0fff Mon Sep 17 00:00:00 2001
From: Tami Love <87874774+tmalove@users.noreply.github.com>
Date: Mon, 30 Aug 2021 11:57:36 -0400
Subject: [PATCH] Added etcd as a control plane option

[OSDOCS-2343]  Added support for etcd as a control plane component in configuring TLS security profiles section, as of OpenShift 4.9.
---
 security/tls-security-profiles.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/security/tls-security-profiles.adoc b/security/tls-security-profiles.adoc
index d859213a535a..f07d6c8ebd80 100644
--- a/security/tls-security-profiles.adoc
+++ b/security/tls-security-profiles.adoc
@@ -12,9 +12,9 @@ Cluster administrators can choose which TLS security profile to use for each of
 * the Ingress Controller
 * the control plane
 +
-This includes the Kubernetes API server, Kubernetes controller manager, Kubernetes scheduler, OpenShift API server, OpenShift OAuth API server, and OpenShift OAuth server.
+This includes the Kubernetes API server, Kubernetes controller manager, Kubernetes scheduler, OpenShift API server, OpenShift OAuth API server, OpenShift OAuth server, and etcd.
 +
-// NOTE: etcd and OpenShift controller manager are not included
+// NOTE: OpenShift controller manager are not included
 
 * the kubelet, when it acts as an HTTP server for the Kubernetes API server