Add serviceName support to GameServerSet for individual Pod DNS resolution

[AisenQinjia]

Hello,

I've been working with the OpenKruise Game project, specifically with the GameServerSet custom resource. I noticed that when using GameServerSet, the generated Pods do not have individual DNS records, which seems to be due to the missing subdomain field in the Pods' spec part.

In contrast, when using a StatefulSet with a specified serviceName, the Pods have a subdomain field, which allows for individual DNS resolution for each Pod.

To improve the functionality of GameServerSet, I would like to suggest adding support for a serviceName-like field or directly using the subdomain field. This would enable individual DNS resolution for each Pod managed by a GameServerSet, making it more convenient for use cases that require addressing individual Pods.

Please let me know if this is something that can be considered for implementation in the OpenKruise Game project or if there are any workarounds available to achieve this functionality.

[chrisliu1995]

OKG intends to simplify non-game-related concept fields, so it is planned not to add a serviceName field to users on GameServerSet. However, after the user define GameServerSet, the serviceName with the same name as GameServerSet will be used by default. Is this approach acceptable?

[AisenQinjia]

OKG intends to simplify non-game-related concept fields, so it is planned not to add a serviceName field to users on GameServerSet. However, after the user define GameServerSet, the serviceName with the same name as GameServerSet will be used by default. Is this approach acceptable?

that would be nice, we are using StatefulSet in the same manner as you said above.

[ringtail]

@AisenQinjia pr has been merged.