[docs] Encryption docs update (#6082)
* Bad link in encryption docs * clarifying the guide link * Update website/source/docs/agent/encryption.html.md Co-Authored-By: kaitlincarter-hc <43049322+kaitlincarter-hc@users.noreply.github.com> * Update website/source/docs/agent/encryption.html.md Co-Authored-By: kaitlincarter-hc <43049322+kaitlincarter-hc@users.noreply.github.com>
This commit is contained in:
parent
0d8e2c0d25
commit
f330619621
|
@ -101,7 +101,9 @@ and is secured using a symmetric key. See above for enabling gossip encryption.
|
||||||
## Configuring TLS on an existing cluster
|
## Configuring TLS on an existing cluster
|
||||||
|
|
||||||
As of version 0.8.4, Consul supports migrating to TLS-encrypted traffic on a running cluster
|
As of version 0.8.4, Consul supports migrating to TLS-encrypted traffic on a running cluster
|
||||||
without downtime. This process assumes a starting point with no TLS settings configured, and involves
|
without downtime. This process assumes a starting point with no TLS settings configured and involves
|
||||||
an intermediate step in order to get to full TLS encryption. Review this step-by-step
|
an intermediate step in order to get to full TLS encryption. Review the
|
||||||
[guide](https://learn.hashicorp.com/consul/security-networking/certificates) to learn how.
|
[Securing RPC Communication with TLS Encryption guide](https://learn.hashicorp.com/consul/security-networking/certificates)
|
||||||
|
for the step-by-step process to configure TLS on a new or existing cluster. Note the call outs there
|
||||||
|
for existing cluster configuration.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue