You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is similar to #2655 except that I don't want to set the external IP; I want minikube to properly report the external IP of the node with the value I can see in minikube ip (see googleforgames/agones#751).
The exact command to reproduce the issue:
minikube start
kubectl get nodes -o wide
The full output of the command that failed:
$ kubectl get nodes -o wide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
minikube Ready master 12m v1.11.0 10.0.2.15 <none> Buildroot 2018.05 4.15.0 docker://18.9.6
If I run the same command against a GKE cluster, I see both an internal IP and external IP populated.
The output of the minikube logs command:
The operating system version: MacOS Mojave 10.14.5
The text was updated successfully, but these errors were encountered:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
This is similar to #2655 except that I don't want to set the external IP; I want minikube to properly report the external IP of the node with the value I can see in
minikube ip
(see googleforgames/agones#751).The exact command to reproduce the issue:
The full output of the command that failed:
If I run the same command against a GKE cluster, I see both an internal IP and external IP populated.
The output of the
minikube logs
command:The operating system version: MacOS Mojave 10.14.5
The text was updated successfully, but these errors were encountered: