Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

etcd_discovery_url is causing terraform to reprovision instances when it doesn't need to #675

Closed
tayzlor opened this issue Mar 9, 2016 · 0 comments

Comments

@tayzlor
Copy link
Member

tayzlor commented Mar 9, 2016

Steps to reproduce -

  • Provision initial cluster
  • Increase number of slaves (+1)
  • Run terraform plan - on this step it will change the cloud config for every instance in the cluster (because we are using the size variable, which is taking into account ALL machines in the cluster)

At the moment we are using a "small cluster" architecture for etcd (see https://coreos.com/os/docs/latest/cluster-architectures.html)

We should move to the "Production cluster" setup running the etcd central services only on the "master" nodes. This would mean we'd have a much more static setup (with either 3 or 5 masters) and allow the slaves to scale as they wish and join the discovery URL for the central etcd cluster. As a result size shouldn't be changing too frequently (unless the number of masters is changed - which is fine), which shouldn't cause terraform to taint resources as much circumventing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant