Fixes version reference in encryption docs.
This commit is contained in:
parent
e32b42a222
commit
536915fa9a
|
@ -113,7 +113,7 @@ 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.3, 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:
|
an intermediate step in order to get to full TLS encryption:
|
||||||
|
|
||||||
|
@ -127,4 +127,4 @@ everywhere but the agents will not yet be enforcing TLS.
|
||||||
if applicable) to `true`.
|
if applicable) to `true`.
|
||||||
4. Perform another rolling restart of each agent in the cluster.
|
4. Perform another rolling restart of each agent in the cluster.
|
||||||
|
|
||||||
At this point, full TLS encryption for RPC communication should be enabled.
|
At this point, full TLS encryption for RPC communication should be enabled.
|
||||||
|
|
Loading…
Reference in New Issue