agones-dev/agones

Example: https://console.cloud.google.com/cloud-build/builds/33c0c82b-73d7-487e-a41c-d4c81e389d4e?project=agones-images It's the first time I'm seeing this one, this might need investigation: === RUN TestFleetStrategyValidation === PAUSE TestFleetStrategyValidation === CONT TestFleetStrategyValidation fleet_test.go:110: Error Trace: /go/src/agones.dev/agones/test/e2e/fleet_test.go:110 /go/src/agones.dev/agones/test/e2e/fleet_test.go:119 Error: "[]" should have 1 item(s), but has 0 Test: TestFleetStrategyValidation time="2026-08-31 21:14:38.707" level=info msg="Checking Fleet Ready replicas" expected=10 fleet=scale-fleet-0-9kvc2 fleetStatus="{Replicas:10 ReadyReplicas:3 ReservedReplicas:0 AllocatedReplicas:0 Allocations:0 Players:<nil> Counters:map[] Lists:map[]}" test=TestScaleUpAndDownInParallelStressTest time="2026-08-31 21:14:38.915" level=info msg="waiting for fleet condition" fleet=scale-fleet-1-zpnb2 test=T

Example: https://console.cloud.google.com/cloud-build/builds/c32233e8-d92c-461b-8bc2-85188f717dd7;step=2?project=agones-images It just fails sometimes, particularly on Autopilot. Was thinking of just implementing a retry on Autopilot only with a require.WithEventuallyT(...) since it seems stable on Stable, and I'd like to keep the coverage of a single connection. Unless someone can see a reason why it's flaking sometimes. VERBOSE: === RUN TestGameServerTcpProtocol VERBOSE: === PAUSE TestGameServerTcpProtocol VERBOSE: === CONT TestGameServerTcpProtocol VERBOSE: time="2026-08-11 05:02:09.137" level=info msg="GameServer created, waiting for Ready" gs=game-serversmcqj test=TestGameServerTcpProtocol VERBOSE: time="2026-08-11 05:02:09.198" level=info msg="Waiting for states to match" awaitingState=Ready currentState=Creating gs=game-serversmcqj test=TestGameServerTcpProtocol VERBOSE: time="2026-08-11 05:02:10.171" level=info msg="Waiting for states to match" awaitingState=Ready currentSta

What does this feature do? CountsAndLists provides generic integer counter and string-list tracking on GameServers. It enables: Declaring named counters (integer) and lists (up to 1000 string values) on a GameServer at creation time Reading/updating those values via the SDK (GetCounter, UpdateCounter, GetList, UpdateList, AddListValue, RemoveListValue) Filtering GameServerAllocations based on counter/list capacity and priorities Fleet auto-scaling driven by available counter/list capacity Aggregated counter/list status rolled up to Fleet and GameServerSet All SDK methods for this feature live in the beta SDK packages today (Go: sdks/go/beta.go, C#: sdks/csharp/sdk/Beta.cs, Rust: sdks/rust/src/beta.rs, Unity: sdks/unity/AgonesBetaSdk.cs). Current state: Beta (enabled by default since v1.41.0) ⚠️ This is a large, cross-cutting change. It should be broken into multiple PRs to keep reviews manageable. A suggested breakdown is at the bottom of this issue. Acceptance Criteria / Task

Summary The Agones extensions apiserver (agones-controller-service:443/apis/allocation.agones.dev/v1/...) serves as a Kubernetes aggregated APIService. When Kubernetes routes allocation requests through the API server aggregator, the aggregator enforces authn/authz normally. However, the same service port is directly reachable within the cluster as a standard Service endpoint. The extensions HTTPS server (pkg/util/https/server.go) configures TLS with GetCertificate only — no ClientAuth, no RequestHeader CA verification, no bearer-token authentication, and no SubjectAccessReview before dispatching to resource handlers. pkg/util/apiserver/apiserver.go routes /apis/<groupVersion>/namespaces/ directly to CRDHandler delegates without any authorization middleware. As a result, any in-cluster workload that can reach agones-controller-service on port 443 can POST a GameServerAllocation directly, bypassing Kubernetes RBAC for the aggregated resource. Affected files pkg/util/https/server.go

Summary The PlayerTracking feature has been at Alpha (disabled by default) since Agones 1.6.0. CountsAndLists — a superset replacement — has been at Beta (enabled by default) since 1.41.0 and has been stable there for a significant period. The player-tracking docs already carry a deprecation notice pointing users to CountsAndLists. Given that CountsAndLists covers all PlayerTracking use cases and more, and that we are unlikely to revert CountsAndLists, I'd like to propose that we remove PlayerTracking (and the companion PlayerAllocationFilter Alpha feature, which depends on it) in the near future. That said, looking for general consensus before moving forward. Motivation PlayerTracking (Alpha, disabled) has had no meaningful changes in years and predates the generalized CountsAndLists approach. CountsAndLists (Beta, enabled) fully supersedes it: player IDs map to list values, player count/capacity map to counter count/capacity. Keeping PlayerTracking adds maintenance burden across