-
Notifications
You must be signed in to change notification settings - Fork 813
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Agones Getting Started Guide with Minikube uses wrong IP due to minikube bug #751
Comments
Result of kubectl describe node:
|
If you run It makes sense that the minikube node wouldn't be reachable via an internal IP from "outside of the cluster" since that is what internal IP means and generally a gameserver is intended to be reachable externally. The underlying problem seems to be similar to this issue where it's explained that the minikube VM is taking the address of eth0 but eth1 is what is returned by I've opened kubernetes/minikube#4330 against the minikube repo to see if there is something they can fix on that end. If not, we can update the docs specifically for minikube with the workaround you put into the initial bug report. |
Sounds good! Cheers :y:
El El jue, 23 may 2019 a las 10:43, Robert Bailey <notifications@github.com>
escribió:
… If you run kubectl get nodes - o wide on a GKE cluster vs. a minikube
cluster you can see that on the GKE cluster the columns for the internal IP
and external IP of each node is populated while on the minikube cluster
only the column for internal IP is filled in. Looking at the output of kubectl
get gs on the GKE cluster I see the external IP for the node being used
while on the minikube cluster it uses the internal IP (the only one
available).
It makes sense that the minikube node wouldn't be reachable via an
internal IP from "outside of the cluster" since that is what internal IP
means and generally a gameserver is intended to be reachable externally.
The underlying problem seems to be similar to this issue
<kubernetes/minikube#2922 (comment)>
where it's explained that the minikube VM is taking the address of eth0 but
eth1 is what is returned by minikube ip.
I've opened kubernetes/minikube#4330
<kubernetes/minikube#4330> against the minikube
repo to see if there is something they can fix on that end. If not, we can
update the docs specifically for minikube with the workaround you put into
the initial bug report.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#751>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACKYNMB6EQ5KVCGPLBBAM2TPWZKLXANCNFSM4HJI7YLQ>
.
|
My minikube issue was a dupe and I've bumped kubernetes/minikube#3416 which is where the feature is being tracked on that end. If this isn't fixed in minikube before our 1.0 milestone we will definitely update our docs. |
What happened:
Following the Installation and [Getting Started] (https://agones.dev/site/docs/getting-started/create-gameserver/) guide allows the user to have the simple-upd sample server up and running.
The problem is that the minikube reported Node IP for the game server is not correct and does not allow the user to connect to the game server, using the nc command provided.
What you expected to happen:
The main expectation when following the guide is that it works out of the box. The result is that you have a game server running correctly in the cluster, but not able to connect to it, thus not being able to finish the getting started guide.
How to reproduce it (as minimally and precisely as possible):
Follow the steps provided in the links provided above. When getting to the point of doing:
You get something like:
Where the ADDRESS is unreachable when doing:
Anything else we need to know?:
The solution to this problem with the minikube version I am using is to use this command to get the correct ADDRESS:
Then, you can use this IP + the port reported in:
Then you are able to connect.
This has been discussed in the slack channel, and we found this bug reported to minikube:
Environment:
kubectl version
): client 1.13.1 / server 1.11.0The text was updated successfully, but these errors were encountered: