/site/docs/reference/ Recent content in Reference on Agones Hugo -- gohugo.io en /site/docs/reference/gameserver/ Thu, 03 Jan 2019 03:58:48 +0000 /site/docs/reference/gameserver/ A full GameServer specification is available below and in the example folder for reference : apiVersion: "agones.dev/v1" kind: GameServer # GameServer Metadata # https://v1-29.docs.kubernetes.io/docs/reference/generated/kubernetes-api/v1.29/#objectmeta-v1-meta metadata: # generateName: "gds-example" # generate a unique name, with the given prefix name: "gds-example" # set a fixed name 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 is a descriptive name for the port - name: default # [Stage:Alpha] # [FeatureFlag:PortRanges] # range is the optional port range name from which to select a port when using a 'Dynamic' or 'Passthrough' port policy. /site/docs/reference/fleet/ Thu, 03 Jan 2019 03:58:52 +0000 /site/docs/reference/fleet/ To allocate a GameServer from a Fleet, use a GameServerAllocation. Like any other Kubernetes resource you describe a Fleet’s desired state via a specification written in YAML or JSON to the Kubernetes API. The Agones controller will then change the actual state to the desired state. A full Fleet specification is available below and in the example folder for reference : apiVersion: "agones.dev/v1" kind: Fleet # Fleet Metadata # https://v1-29.docs.kubernetes.io/docs/reference/generated/kubernetes-api/v1.29/#objectmeta-v1-meta metadata: name: fleet-example spec: # the number of GameServers to keep Ready or Allocated in this Fleet replicas: 2 # defines how GameServers are organised across the cluster. /site/docs/reference/gameserverallocation/ Sun, 07 Jul 2019 03:58:52 +0000 /site/docs/reference/gameserverallocation/ Allocation is the process of selecting the optimal GameServer that matches the filters defined in the GameServerAllocation specification below, and returning its details. A successful Alloction moves the GameServer to the Allocated state, which indicates that it is currently active, likely with players on it, and should not be removed until SDK.Shutdown() is called, or it is explicitly manually deleted. A full GameServerAllocation specification is available below and in the example folder for reference: /site/docs/reference/fleetautoscaler/ Thu, 03 Jan 2019 03:58:55 +0000 /site/docs/reference/fleetautoscaler/ A full FleetAutoscaler specification is available below and in the example folder for reference, but here are several examples that show different autoscaling policies. Ready Buffer Autoscaling Fleet autoscaling with a buffer can be used to maintain a configured number of game server instances ready to serve players based on number of allocated instances in a Fleet. The buffer size can be specified as an absolute number or a percentage of the desired number of Ready game server instances over the Allocated count. /site/docs/reference/agones_crd_api_reference/ Mon, 01 Jan 0001 00:00:00 +0000 /site/docs/reference/agones_crd_api_reference/ Packages: agones.dev/v1 allocation.agones.dev/v1 autoscaling.agones.dev/v1 multicluster.agones.dev/v1 agones.dev/v1 Package v1 is the v1 version of the API. Resource Types: Fleet GameServer GameServerSet Fleet Fleet is the data structure for a Fleet resource Field Description apiVersion string agones.dev/v1 kind string Fleet metadata Kubernetes meta/v1.ObjectMeta Refer to the Kubernetes API documentation for the fields of the metadata field. spec FleetSpec replicas int32 Replicas are the number of GameServers that should be in this set.