Releases: Octops/gameserver-ingress-controller
v0.1.8
Considering Scheduled, RequestReady and Ready states for triggering reconciles.
That will speed up the creation of the Ingress resource before a SDK.Ready() is called.
Extras:
- Better logging messages
- Ignore Shutdown state
New Store using K8S Informers and Cache
A new store was extracted to its own data struct and has been refactored to use K8S Informers and not direct calls to the K8S Server API.
That removes the load on the api server. Furthermore, saving resources and improving the controller performance.
Additionally, this release bumped Agones to 1.21
Make HAProxy the recommended Ingress Controller
What is new
- Documentation updated to instruct how to use HAProxy as the Ingress Controller based on the feedback provided on #21.
There were no changes on the code base of the controller and users want to use NGINX Ingress controller the Octops controller will perform the same way.
Expose health check and metrics endpoints
Support Custom TLS Secret Name
This release adds support to a custom annotation octops.io/tls-secret-name
.
This instructs the ingress controller to pass down to the ingress resource the secret that has already been provisioned and should be used for TLS.
That has been a request from the community on #13
Support Custom Annotations
Support Ingress Routing Mode
This release is marked mainly by the addition of the Ingress Routing Mode.
That as a request from #6.
Additional features:
- Record events during the creating of resources
v0.1.1
- CertManager 1.6.0
- Kubernetes 1.22
- Agones 1.18