What happened:

I attempted to use the new feature in v1.41.0 to set my portPolicy to None and when my gameserver started, the gameserver's port in its status was set to 0. My gameserver code was written to take the Address and Port from the gameserver's status and use them for connections. When the port is 0, this failed.

What you expected to happen:

My expectation is perhaps that when portPolicy is set to None, the Port field of the gameserver's status would become equal to the containerPort value. In other words, to connect to a gameserver Pod with a None portPolicy, I would use the PodIP and the containerPort to connect.

How to reproduce it (as minimally and precisely as possible):

Use any gameserver spec and set its portPolicy to None.

portPolicy:
  - name: game
    portPolicy: None
    protocol: UDP
    containerPort: 1234

Check the status once the gameserver is running:

Anything else we need to know?:

Environment:

• Agones version: v1.41.0
• Kubernetes version (use kubectl version): v1.30.0-eks-036c24b
• Cloud provider or hardware configuration: AWS EKS
• Install method (yaml/helm): Helm
• Troubleshooting guide log(s):
• Others: