Skip to content

Commit 555c0f3

Browse files
committed
wajiha feedback ++
1 parent 2468cc7 commit 555c0f3

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
{{es}} transport security and TLS certificates are automatically configured by the operator, but you can still [customize its service and CA certificates](/deploy-manage/security/k8s-transport-settings.md).
1+
{{es}} transport security and TLS certificates are automatically configured by the operator, but you can still [customize the {{es}} transport service, certificate authority, and certificates](/deploy-manage/security/k8s-transport-settings.md).

deploy-manage/security/k8s-transport-settings.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ When you change the `clusterIP` setting of the service, ECK deletes and re-creat
3939

4040
## Configure a custom Certificate Authority [k8s-transport-ca]
4141

42-
{{es}} uses X.509 certificates to establish encrypted and authenticated connections across nodes in the cluster. By default, ECK creates a self-signed CA certificate to issue a certificate [for each node in the cluster](/deploy-manage/security/set-up-basic-security.md#encrypt-internode-communication).
42+
{{es}} uses X.509 certificates to establish encrypted and authenticated connections across nodes in the cluster. By default, ECK creates a CA to issue a self-signed certificate [for each node in the cluster](/deploy-manage/security/set-up-basic-security.md#encrypt-internode-communication).
4343

4444
You can use a Kubernetes secret to provide your own CA instead of the self-signed certificate that ECK will then use to create node certificates for transport connections. The CA certificate must be stored in the secret under `ca.crt` and the private key must be stored under `ca.key`.
4545

deploy-manage/security/secure-cluster-communications.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -67,9 +67,9 @@ The way that transport layer security is managed depends on your deployment type
6767
{{es}} transport security is fully managed by Elastic, and no configuration is required.
6868
::::
6969

70-
::::{admonition}{tab-item} ECE
70+
::::{tab-item} ECE
7171
:sync: ece
72-
{{es}} transport security is fully managed by {{ece}} platform, and no configuration is required.
72+
{{es}} transport security is fully managed by the {{ece}} platform, and no configuration is required.
7373
::::
7474

7575
::::{tab-item} ECK

0 commit comments

Comments
 (0)