Closed Lahamc closed 7 months ago
I have tested it on Debian rodete (amd64)
with minikube v1.32.0
.
Installed the Agones using helm (https://agones.dev/site/docs/installation/install-agones/helm/#installing-the-chart).
Also Created GameServer using this link kubectl create -f https://raw.githubusercontent.com/googleforgames/agones/release-1.39.0/examples/xonotic/gameserver.yaml
Everything worked perfectly fine for me. Refer this link for complete GameServer Specifications https://agones.dev/site/docs/reference/gameserver/. Checkout the Xonotic gameserver yaml https://github.com/googleforgames/agones/blob/main/examples/xonotic/gameserver.yaml Also try with default portPolicy and protocol?
I have tested it on
Debian rodete (amd64)
withminikube v1.32.0
. Installed the Agones using helm (https://agones.dev/site/docs/installation/install-agones/helm/#installing-the-chart). Also Created GameServer using this linkkubectl create -f https://raw.githubusercontent.com/googleforgames/agones/release-1.39.0/examples/xonotic/gameserver.yaml
Everything worked perfectly fine for me. Refer this link for complete GameServer Specifications https://agones.dev/site/docs/reference/gameserver/. Checkout the Xonotic gameserver yaml https://github.com/googleforgames/agones/blob/main/examples/xonotic/gameserver.yaml Also try with default portPolicy and protocol?
For the game server xonotic:1.8, it also worked perfectly fine for me. My problem is that I am using my own game server image and the error that I encountered is very similar to the error that I found in gcr.io/agones-images/xonotic-example:0.5 image. Therefore, I wanna know what is probably happening to my game server. Actually I am using node js for my game server. Am I supposed to call SDK.health() and SDK.ready() in my game server even though there is a agones-gameserver-sidecar in my kubernetes pod?
I have tested it on
Debian rodete (amd64)
withminikube v1.32.0
. Installed the Agones using helm (https://agones.dev/site/docs/installation/install-agones/helm/#installing-the-chart). Also Created GameServer using this linkkubectl create -f https://raw.githubusercontent.com/googleforgames/agones/release-1.39.0/examples/xonotic/gameserver.yaml
Everything worked perfectly fine for me. Refer this link for complete GameServer Specifications https://agones.dev/site/docs/reference/gameserver/. Checkout the Xonotic gameserver yaml https://github.com/googleforgames/agones/blob/main/examples/xonotic/gameserver.yaml Also try with default portPolicy and protocol?For the game server xonotic:1.8, it also worked perfectly fine for me. My problem is that I am using my own game server image and the error that I encountered is very similar to the error that I found in gcr.io/agones-images/xonotic-example:0.5 image. Therefore, I wanna know what is probably happening to my game server. Actually I am using node js for my game server. Am I supposed to call SDK.health() and SDK.ready() in my game server even though there is a agones-gameserver-sidecar in my kubernetes pod?
It was my mistake. Misunderstood the concept of agones. I should call the SDK.health() and ready() in my gameserver. It is working now. Thank you so much for the reply.
I am using kubernetes in minikube with agones installed by helm.
Everytime I started my gameserver, the state of my gs turned unhealthy. After I traced the log, I found that agones-gameserver-sidecar keep saying game server health check failed. Therefore, I set my game server health check to disabled. Then my gameserver stuck at scheduled state.
Can anyone tell me what is happening to my game server?
My game server yaml file:
I can reproduce this issue using image gcr.io/agones-images/xonotic-example:0.5.