-
Notifications
You must be signed in to change notification settings - Fork 343
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
Request use of AWS Elastic IP support #223
Comments
This works for creating the instance, EIP, association: Providersprovider "aws" { Variable Declarationsvariable "ami-sles15sp5payg" { variable "key-name" { Create EC2 instanceresource "aws_instance" "demo-instance" { Resource block for eipresource "aws_eip" "demo-1" { Associate the EIPresource "aws_eip" "demo-2" { |
I ran into this problem as well. I shut down the two instances to save money over the weekend, and when they powered up again, they received different IP addresses.
Now I have to manually dig around and destroy the infrastructure I was using to evaluate Rancher. It would be great if the quickstart could be refactored to get the current IP before attempting helm operations in Terraform, or just use an EIP as suggested above. |
This keeps the public ip static. Changes to the instance, e.g. shutdown/start, will not cause an assignment of a new public IP address anymore. Solves issues were destroy failed at 'rancher2_bootstrap' and 'rancher2_cluster_v2' because the public ip was already removed. Fixes: rancher#223 Fixes: rancher#242
Issue: By using a public IP (not EIP), things like Nginx are bound to that temporary IP. If you shutdown/start the instance, you get a different IP resulting in 'bad gateway' when accessing the API.
One way this project could be even more helpful would be to support EIP on deployment. Example:
The text was updated successfully, but these errors were encountered: