Scenario: You're deploying Consul in a dedicated environment, and due to the complex network layout, you are forced to funnel traffic through a firewall that will perform
a NAT (network address translation) for the Consul node. What configuration parameter can be used to identify what IP address that the other nodes in the cluster should
Scenario: You have an application that uses Consul service discovery to connect to backend services in order to process data submitted by end-users. The front-end web
service consists of 3 containers, while the backend service consists of 5 static virtual machines. All of the front-end web servers and the backend servers are registered
with Consul.
During normal operations, a user complains that the data processing is taking too long. To troubleshoot, you run a DNS query against the DNS name for the backend
service, but discover that the response only contains three of the virtual machines. Why would Consul only respond with three servers rather than all five?
You have a Consul cluster running production workloads in your environment. However, you've discovered that the cluster was initially deployed without gossip
encryption configured, which means that traffic is being sent in cleartext. The security team has requested this to be updated ASAP. However, you can't take an outage on
the Consul service right now, knowing the server nodes will stop communicating once you start editing the configuration files one by one.
How can you enable gossip encryption on the existing cluster without affecting the services it is currently providing the business?