Elastic Ip

[cescoferraro]

My use case for elastic ips is dns. So I can point Route53 to it,then kill/create the actual EC2 as many times as I want which is very useful for handling machine crashes

I think this is AWS specific. AFIK DO does not change the droplet ip when assigning a Floating ip but AWS does.

I have assigned a elastic ip to the EC2, and this changes the machine ip making the certs invalid.
52.67.88.239 is my elastic ip. Is there a way I can regenerate certs to a specific ip address like 52.67.88.239?

cescoferraro@mint-pro: ~/code/go/src/github.com/cescoferraro
$ kmachine create -d amazonec2 --k8s-version 1.3.0-alpha.2 cescoferraro.xyz
Running pre-create checks...
Creating machine...
Waiting for machine to be running, this may take a few minutes...
Machine is running, waiting for SSH to be available...
Detecting operating system of created instance...
Provisioning created instance...
Rebooting system...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Configuring kubernetes...
Copying certs tregenerate-certso the remote system...
To see how to connect Docker to this machine, run: kmachine env cescoferraro.xyz
cescoferraro@mint-pro: ~/code/go/src/github.com/cescoferraro
$  kmachine env cescoferraro.xyz
Error running connection boilerplate: Error checking and/or regenerating the certs: There was an error validating certificates for host "52.67.88.239:2376": x509: certificate is valid for 52.67.165.230, not 52.67.88.239

Currently regenerate-certs tries to ssh to the old ip

cescoferraro@mint-pro: ~/code/go/src/github.com/cescoferraro
$ kmachine regenerate-certs cescoferraro.xyz
Regenerate TLS machine certs?  Warning: this is irreversible. (y/n): y
Regenerating TLS certificates
Error getting SSH command: Something went wrong running an SSH command!
command : cat /etc/os-release
err     : exit status 255
output  :