Randy Fay

@sworisbreathing I expect to test this week or at least soon. Do you mind if I push an extra commit or two into your branch? (Changing 0.8.2 to 0.8.3 for...

I don't think we will end up doing this, but patches are welcome. I was hoping to switch to using stateful sets instead, which would also work on AWS I...

Thanks so much for the report. We haven't given it a shot yet, please do report back with anything you learn. Thanks!

I recommend reporting that behavior with your config on the [consul list](https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!forum/consul-tool) - also, make sure you didn't end up doing any IP address changes, as consul goes crazy when...

I note this conversation on the Consul list that sounds like exactly your situation: https://groups.google.com/d/msg/consul-tool/dRA-cEBUnz8/9KGrFS0pDQAJ

I note that this seems to be addressed in the [still-unreleased 0.8.1](https://github.com/hashicorp/consul/blob/master/CHANGELOG.md#081-unreleased) (https://github.com/hashicorp/consul/pull/2884): > agent: Node IDs derived from host information are now hashed to prevent things like common server...

It looks to me like a very simple technique to solve this problem is [-disable-host-node-id](https://www.consul.io/docs/agent/options.html#_disable_host_node_id); this stops using the host as source for a unique node id and creates a...

And... 0.8.1 was released today

Thanks for your work on this! It won't surprise me if the stateful sets approach is too disruptive for us at this point. Of course your excellent https://github.com/drud/vault-consul-on-kube/pull/18 may be...

@rickmanelius the 0.8 series eventually put in a solution for this problem. Doesn't mean we have the bandwidth to work on it right now.