Connecting timeout while retrieving nodeup.sha1 (via S3 bucket)

[jbye]

I have been trying to configure my master for some time no with no success. Logging in to the master reveals that there's a curl process stuck on resolving retrieving nodeup.sha1.

curl -f --ipv4 -Lo nodeup.sha1 --connect-timeout 20 --retry 6 --retry-delay 10 https://kubeupv2.s3.amazonaws.com/kops/1.4.1/linux/amd64/nodeup.sha1

Resolving kubeupv2.s3.amazonaws.com (kubeupv2.s3.amazonaws.com)... 52.216.0.248 Connecting to kubeupv2.s3.amazonaws.com (kubeupv2.s3.amazonaws.com)|52.216.0.248|:443... failed: Connection timed out. Retrying.

[jbye]

It is clear that instances within the kubernetes VPC created by Kops are not able to communicate over the internet when the master is configured without a public IP.

Correct me if I am wrong, but with no public IP on the master, and with Kops assigning an Internet Gateway to the subnet, then there's no wonder the master cannot go "online"?

Is the master required to have a public IP in such a configuration?

[jbye]

Seems there's no support for the kind of setup I was trying to achieve (private subnet); #428