Use Elastic IPs for the various instances #62
Comments
hferentschik
added a commit
to hferentschik/terraform-aws-openshift
that referenced
this issue
Oct 17, 2018
… instance restarts
dwmkerr
added a commit
that referenced
this issue
Oct 23, 2018
Issue #62 Using Elastic IPs for the AWS instances allowing for instan…
|
Just merged into |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If Elastic IPs are used for each instance, the whole cluster can be stopped and restarted without any issues. This allows to create the cluster once and only start it when needed.
Atm, a restart of the cluster leads new IPs getting assigned to the instances, making it hard to ssh into the machine and even worse breaking the public route of the master.
Since aws_eip does not have a public DNS attribute (see hashicorp/terraform-provider-aws#1149) and since the DNS attribute of the instance does not get updated once the Elastic IP is assigned, one needs for now to remove the use of public DNS names of the nodes. This does not have any impact on the functionality of the cluster though.
The text was updated successfully, but these errors were encountered: