-
Notifications
You must be signed in to change notification settings - Fork 828
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
Installation error on Google Cloud GKE Autopilot #2249
Comments
May I add that besides this error, it would appear that agones has been mostly installed and is running:
|
There's a variety of reasons why GKE autopilot won't work - the primary one being that they do arbitrarily delete nodes, since they are targeted at stateless workloads. So unfortunately, I have to close this as |
For the gameservers I have in mind they are tolerant to being arbitrarily deleted and can continue to function as long as they shortly reallocated, if they are given a signal they can even gracefully shutdown without disruption and migrate to a replacement gameserver. This makes the Autopilot system a good fit for my use case. How stateful are the agones components? I'd like to take a look at this if possible, I'm relatively new to the specifics of Kubernetes so I'd be grateful for any pointers on this. |
It's also not possible because Autopilot doesn't support core functionality of Agones such as hostPorts, mutation and validation webhooks, etc. Sorry, there's no way for it to work. It's not built for this kind of workload. |
What happened:
I followed the guide on https://cloud.google.com/game-servers/docs/quickstart however instead of the suggested cluster configuration, I decided to create a Google Cloud Autopilot cluster, when I tried to install Agones I recieved this error from:
kubectl apply -f https://raw.githubusercontent.com/googleforgames/agones/release-1.16.0/install/yaml/install.yaml
Environment:
kubectl version
):Questions:
The text was updated successfully, but these errors were encountered: