Add selectable fields to gameserver crd#4542
Add selectable fields to gameserver crd#4542swermin wants to merge 3 commits intoagones-dev:mainfrom
Conversation
0ac0047 to
19769ae
Compare
|
Hello ! |
|
Ah, good point! Let me do that |
19769ae to
e3d0054
Compare
|
/gcbrun |
|
Is there any limit on the number of selectable fields we can apply? |
I don’t think so. What do you have in mind? |
|
Seems that there is indeed a limitation of 8 selectable fields per CRD: https://pkg.go.dev/k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1#CustomResourceDefinitionVersion Might not be an issue, but we can keep an eye on it, I guess these selectable fields makes sense ? |
|
I thought I read that there was a limit! |
And you were right 😄 |
|
I don't have any issues with these fields - but we should be careful with what we pick. |
|
Build Succeeded 🥳 Build Id: 29903f9c-f2fe-4012-9b70-99c9de2f1bc6 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: |
I cannot seem to read the manual 🤣 |
I get that. These fields would help us make our maintenance cycle simpler, but that doesn’t mean that it is a right choice to put in here. Our gameservers (for now) do not support signals. So we have These selectors would make is so that we can run a more simple command, like: |
59eee73 to
18f72c6
Compare
|
I have a fun idea - why not make selected fields helm configurable, and we can default to the two you have selected already. We don't use them internally, and that way, anyone can change them should they need to. WDYT? |
|
I was actually wondering if that was possible. Because it would make sense to give the option for others to set the ones they need (if needed that is) |
18f72c6 to
8c3c002
Compare
|
I’ll do some tinkering! |
|
I am also fine to keep the selectable fields empty if that is preferred! |
50fa821 to
0a3e5d1
Compare
0a3e5d1 to
41a1655
Compare
Signed-off-by: Ermin Hrkalovic <ermin.hrkalovic@guerrilla-games.com>
Signed-off-by: Ermin Hrkalovic <ermin.hrkalovic@guerrilla-games.com>
Signed-off-by: Ermin Hrkalovic <ermin.hrkalovic@guerrilla-games.com> Co-authored-by: Copilot <copilot@github.com>
41a1655 to
f1d2062
Compare
|
/gcbrun Love it. Thinking about docs. We'll definitely need docs here: https://agones.dev/site/docs/installation/install-agones/helm/#gameservers But wondering where to put that fields are selectable in the docs -- maybe in here? https://agones.dev/site/docs/reference/gameserver/ ? |
|
Build Succeeded 🥳 Build Id: ce0a1c5f-8861-4e04-a822-c7b9442e823c 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: |
What type of PR is this?
/kind feature
What this PR does / Why we need it:
We have observers to make sure that our servers are being in the right state. Since we are running with multi servers it is hard to find specific servers with fields like
statusandnodeName. So, to facilitate the filtering we wanted to add those fields as selectable.Special notes for your reviewer:
This is a nice to have feature, to be able to filter based on fields like state and node name.