Skip to content

Move to multiple dynamic range ports #1911

@WeetA34

Description

@WeetA34

Hi Mark,

Our game server uses 4 passthrough ports:

  • 1 game port
  • 3 tools ports
    I would like to have the game port opened to the whole universe but not the 3 tools ports for which i want to allow only some sources

Proposal:
I imagine we can move port range (gameservers.minPort and gameservers.maxPort) to a list of port ranges and choose the port range to use in the game server ports definition.
So, we can define a different firewall rule for each range.

ie.
install values:

...
gameservers:
  namespaces: ["default"]
  ranges:
  - name: game
    minPort: 7000
    maxPort: 7099
  - name: tools
    minPort: 7100
    maxPort: 7199

and gamerserver definition:

apiVersion: "agones.dev/v1"
kind: GameServer
...
spec:
  # if there is more than one container, specify which one is the game server
  container: example-server
  # Array of ports that can be exposed as direct connections to the game server container
  ports:
  - name: default
    range: game
    portPolicy: Passthrough
    protocol: UDP
  - name: tool1
    range: tools
    portPolicy: Passthrough
    protocol: TCP
  - name: tool2
    range: tools
    portPolicy: Passthrough
    protocol: TCP
  - name: tool3
    range: tools
    portPolicy: Passthrough
    protocol: TCP
...

Workaround:
If the game port is UDP and Tools ports are TCP, you can only filter sources for TCP destinations.
But it's not possible if you want to apply different firewall rules for the same protocol

Thank you
Regards
Stéphane

Metadata

Metadata

Assignees

No one assigned

    Labels

    awaiting-maintainerBlock issues from being stale/obsolete/closedhelp wantedWe would love help on these issues. Please come help us!kind/featureNew features for Agones

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions