I noticed all the nodes created by GKE have ephemeral external IPs.
Is this necessary and can it be disabled? I'd rather not expose all nodes publicly.
To add a node pool to an existing cluster, perform the following steps: Go to the Google Kubernetes Engine page in the console. In the cluster list, click the name of the cluster you want to modify. Click add_box Add node pool.
Kubernetes assigns an IP address (the Pod IP) to the virtual network interface in the Pod's network namespace from a range of addresses reserved for Pods on the node. This address range is a subset of the IP address range assigned to the cluster for Pods, which you can configure when you create a cluster.
create a dedicated IAM service account. create kube config with tokens for both clusters by doing gcloud container clusters get-credentials clusterA and gcloud container clusters get-credentials clusterB. use that kube config file in client-go via BuildConfigFromFlags on clusterA.
I noticed all the nodes created by GKE have ephemeral external IPs. Is this necessary?
Yes. GCE VMs need an external IP address to make outbound requests to the internet, which includes the GCE APIs. Without external IPs, the VMs wouldn't be able to connect to the cluster control plane (Kubernetes apiserver), docker hub, gcr.io, etc.
Can it be disabled?
Not at the current time.
Just a quick comment for the future traveler. This is still not possible as of today but they are working on it
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With