Upgrade mechanism #354
-
I have a big question about the upgrading of a server with Shulker. In my case, let's say I want to upgrade a plugin on one of my server fleets (proxy or not). I change the value of my url in env vars, which will be downloaded when my server starts up, and send it to kube. But we agree that kube will automatically kill all servers to apply the change, and automatically kick players. That's not what we'd generally want. Do you think there would be a mechanism to wait until the end of a game session (like in a mini-game) before launching the upgrade? Or simply not lauchn the upgrade on servers already running and simply apply it to new servers? What do you think about this subject? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
Hi, Agones has some nice documentation about this specific use case. You have to tell Agones that a server is Shulker does automatically the job of setting the Agones provides an SDK with appropriate methods. They do not however give a Java implementation. I created one for Shulker that you can use directly:
It does not contain any Javadoc for now, I was not expecting someone to use it, but you absolutely can. I use it in a large Shulker cluster :) It is published in my personal Maven here. If you believe Shulker (the operator) could help you doing that for you, do not hesitate, I'm open to the discussion and if it fits the project I would love to implement it. |
Beta Was this translation helpful? Give feedback.
I did an implementation (still untested but will do shortly). You will find the corresponding issue here: #355 (and the ongoing implementation here)