github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fixes version reference in encryption docs.

Browse Source
pull/3124/head
James Phillips 8 years ago committed by GitHub
parent fa8a26ad54
commit bc3b68ba80
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File

4
website/source/docs/agent/encryption.html.md
Unescape View File

@ -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.

Write Preview
Loading…
Cancel
Save