While etcd was born in the cloud era, it does not really play well in a dynamic environment where nodes come and go and where IP addresses are ephemeral. Moreover, etcd is meant – with its RAFT algorithm at the core – as a consistent key-value store. It rather refuses to form or join a cluster than putting concistency at risk. As a consequence it is very conservative in implementing advanced cluster member management mechanisms – or even heuristics to make the operation of an etcd cluster more comfortable for the admin. The elastic-etcd binary experiments with those advanced member management heuristics. It is meant as a frontend to the etcd binary, applying these heuristics and then creating a matching command line for etcd itself.

1. COREOS FEST BERLIN
ELASTIC ETCD
AN EXPERIMENT TURNINGPETS INTO CATTLES
Dr. Stefan Schimanski, sttts@github, @the1stein

2. https://discovery.etcd.io

3. https://discovery.etcd.io

5. https://discovery.etcd.io

6. https://discovery.etcd.io

7. https://discovery.etcd.io

8. https://discovery.etcd.io

9. https://discovery.etcd.io

10. https://discovery.etcd.io

12. https://discovery.etcd.io

13. https://discovery.etcd.io

14. https://discovery.etcd.io

15. https://discovery.etcd.io

16. https://discovery.etcd.io

17. https://discovery.etcd.io

57. AWS ROLLING UPDATES

58. SERVICE ABSTRACTION IN KUBERNETES

60. SERVICE ABSTRACTION IN KUBERNETES

61. SERVICE ABSTRACTION IN KUBERNETES

62. WEAVEWORKS FLUX

63. WEAVEWORKS FLUX