Lab 2.2: Setup CP node using AWS Elastic IP

ivanr5

I went with the AWS as a provider for this course. I'm going to start/stop VMs a lot to save usage costs. As such, it seems like a reasonable idea to instead pay a small amount for an AWS Elastic IP so that VMs had the same public IP each time they are started. The issue seems to be that Elastic IP is not discovered via ip addr command so auto-generated certificate does not cover it.

Any tips on how to tweak the k8scp.sh script to make use of the AWS Elastic IP? I've come across the kubeadm init --apiserver-advertise-address flag but not sure of that will do the trick.

chrispokorni

Hi @ivanr5,

It is not wise to build out the cluster on public IP addresses. Instead, use the private IP addresses of the VMs, for the init process. What I noticed so far is that in different flavors of the same guest OS, the behavior of the commands that display the host private IP vs public IP, may slightly differ.

The private IP addresses should not change between restarts; and there is no need to pay for static public IPs either. I do not remember having to jump thru hoops to get my cluster up and running on EC2s, as long as both instances were in the same SG, and all ingress traffic was allowed by the SG rule.

Regards,
-Chris