Re: Consul Encryption in CF v234+
Amit Kumar Gupta
Hi Carsten,
That's a good question. We haven't built anything specifically to support 0-downtime for the DEAs, but we have some upcoming changes to make the etcd used by etcd-metric-server, routing-api, all loggregator components, and HM9k also switch to TLS. This would affect all the metron agents colocated on all the VMs, and we're building out a component to support a 0-downtime transition. This work is currently in flight: https://www.pivotaltracker.com/epic/show/2566951 You could apply this concept to consul: * create a new secure (TLS) consul cluster * replace the existing consul cluster (don't change the job name or IPs, just what processes it runs) with an HTTP proxy that proxies requests to the secure cluster * roll out the new IPs and TLS credentials to all clients of the consul cluster * after that deploy is done, nothing should be talking to the HTTP proxy, and you can simply delete that job. Best, Amit On Fri, Jun 24, 2016 at 8:46 AM, Long Nguyen <long.nguyen11288(a)gmail.com> wrote:
|
|