terraform-kubernetes-installer

terraform-kubernetes-installer copied to clipboard

Currently, after a k8s cluster has been created, etcd nodes cannot successfully be replaced. This is a limitation due to how the etcd cluster is created. The current method is to use a discovery url. Switching this to a more convention list of etcd endpoints would allow for more flexible etcd nodes within the installer cluster.

Move from using discovery_url to configure the cluster to building a list of cluster ips, or dns names to allow for terraform node udpates or replacements.

This is an important feature to have so that recovery can be automated.

+1

currently I can update etcd settings to add/remove members across ad's and run terraform. what would the result of this run be? Would this potentially break my cluster? if so, should this be changed to a noop/failure of run?