-
Notifications
You must be signed in to change notification settings - Fork 819
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
Changed how GameServer POD names are generated #565
Conversation
Build Failed 😱 Build Id: 0c41fa66-6bfc-45bc-92e0-06eea5e9c26f To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
pod.ObjectMeta.GenerateName = "" | ||
// Pods inherit the name of their gameserver. It's safe since there's | ||
// a guarantee that pod won't outlive its parent. | ||
pod.ObjectMeta.Name = gs.ObjectMeta.Name |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested this locally and it seems work.
We will need to add a section here in the gameservers controller, such that if |
Instead of generating name based on GS prefix, we take GS name as-is. This is safe, since Pods are owned by Gameservers, so their lifetime is a subset of that of GS, thus we won't have accidental pod name collisions.
8c80e70
to
a0425a1
Compare
Done. |
Build Succeeded 👏 Build Id: 2109198a-6f83-4f35-b52f-621b8467b613 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎆 Noice 🎆
Instead of generating name based on GS prefix, we take GS name as-is.
This is safe, since Pods are owned by Gameservers, so their lifetime is a subset of that of GS, thus we won't have accidental pod name collisions.
This fixes #490