-
Notifications
You must be signed in to change notification settings - Fork 779
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
Custom gameserver configuration not working on containerized local SDK #3630
Labels
kind/bug
These are bugs.
Comments
Thanks for submitting this bug! I think there are three things we can fix here:
I think that will cover it! |
Brilliant, thank you. I will try moving the relevant fields into |
Can confirm that the suggested fix does it:
Correctly retrieving my test list capacity and values now 🎉 . |
Awesome! Good pickup! It took @igooch and I a minute to work out what was going on when we looked at the code! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened:
I have set up a dockerised SDK with a custom
gameserver.yaml
manifest, as per the documentation here:https://agones.dev/site/docs/guides/client-sdks/local/#running-local-mode-in-a-container
I'm using this command:
Note that it's practically the command as suggested by the guide, with the addition of
CountsAndLists
, which I'm trying to test.My yaml includes the following lines:
The container runs, the volume works, and the template seems to be linked properly. In addition to that, changes to the yaml are reflected on the containerised app:
However, when inspecting the gameserver, a different specification is returned:
What you expected to happen:
The SDK container runs and any game server is created using my gameserver template. My custom lists and metadata are created and present in the server.
How to reproduce it (as minimally and precisely as possible):
gameserver.yaml
with predefined lists and metadata.curl -GET "http://localhost:9358/gameserver" -H "accept: application/json"
Anything else we need to know?:
Environment:
kubectl version
): Most likely irrelevant for this issue, but v1.27.3The text was updated successfully, but these errors were encountered: