control
control copied to clipboard
k8s nodes do not have external IP
Describe the bug Kubernetes nodes created by control do not have EXTERNAL-IP assigned even though underlying infrastracture has.
To Reproduce Steps to reproduce the behavior:
- Spin up cluster
- get kubeconfig on your machine
-
kubectl get no -o wide
Actual result
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
ip-10-2-129-171 Ready master 12m v1.13.4 10.2.129.171 <none> Ubuntu 16.04.5 LTS 4.4.0-1072-aws docker://17.6.0
ip-10-2-129-25 Ready <none> 11m v1.13.4 10.2.129.25 <none> Ubuntu 16.04.5 LTS 4.4.0-1072-aws docker://17.6.0
Expected behavior External IPs are assigned likewise in GKE
NAME STATUS ROLES AGE VERSION EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
gke-cka-study-default-pool-7213a7e7-6s3q Ready <none> 10m v1.11.7-gke.4 35.194.30.15 Container-Optimized OS from Google 4.14.89+ docker://17.3.2
gke-cka-study-default-pool-7213a7e7-8xt9 Ready <none> 10m v1.11.7-gke.4 35.202.49.46 Container-Optimized OS from Google 4.14.89+ docker://17.3.2
gke-cka-study-default-pool-7213a7e7-xw05 Ready <none> 10m v1.11.7-gke.4 35.202.55.19 Container-Optimized OS from Google 4.14.89+ docker://17.3.2