v0.3.0

What is new

• Support ingressClassName #47

v0.2.9

What

• Bug Fix #57

Image Tag: octops/gameserver-ingress-controller:0.2.9

v0.2.8

What changed

Added the max-concurrent-reconciles flag (#58)
The previous default was 1 and it is now 10. Users can now set the concurrency according to their needs. This is particularly important for users running large game fleets that might trigger thousands of updates.

v0.2.7

What is new

Dependencies Updates

• Go 1.20
• Agones 1.33
• K8S 1.27.4
• Controller Runtime 0.15.0

Docker Image Released

• docker pull octops/gameserver-ingress-controller:0.2.7

v0.2.6

What is new

• Do not add the TLS section to Ingress if terminate TLS is false #50
• Manifests updates

v0.2.5

What is new

• The service created by the controller is now a headless service. That reduces the load on the kubernetes cluster and network components when deploying fleet bigger than 5K game servers
• Reconciler is less verbose and it will log when new ingress resource is created/updated

v0.2.4

What is new

The controller now supports multiple domains for both routing modes. That means the game server can be accessed by triggering requests to any of the configured domains.

This configuration must be part of the Fleet annotation as the example below:

annotations:
  # Domain Mode
  octops.io/gameserver-ingress-domain: "example.com,example.gg"
  # Path Mode
  octops.io/gameserver-ingress-fqdn: "www.example.com,www.example.gg"

v0.2.3

• Update Agones to 1.28
• Update Go to 1.19

v0.2.2

• Add .Port field to the the list of fields available to use with template #40
• Support custom annotations that are only assigned to Services octops.service- Docs

v0.2.1

This release includes a few new features

• Ability to use Templates on custom annotations #32
• Support custom annotations for Services #29
• Consider RequestReady, Scheduled and Ready as states that can trigger a reconcile event #28
• Annotate the GameServer with octops.io/ingress-ready: true when an ingress resources is created successfully #31

Improvements

• Implementing Kubernetes Informer pattern to offload the the K8S API
• Better logic to handle the events queue while handling events and forgetting objects