Currently, the Kubernetes Gateway’s status.addresses field is populated from the GatewayProxy’s statusAddress, which must be manually configured and updated whenever the Service’s external IP changes.
By allowing the GatewayProxy to reference a Kubernetes Service (e.g., like how control plane is referenced), the controller could automatically fetch the Service’s external IP and propagate it to the Gateway’s status.addresses field. This would make the Gateway’s status self-updating and fully aligned with the actual ingress Service state.
Such functionality would:
- Eliminate manual updates to
statusAddress
- Ensure the Gateway always exposes the correct external address