Stable Egress Controller 0.1.1 lowers the controller’s Hetzner Cloud API usage so it no longer risks hitting the hourly request limit during normal operation.
- The controller now fetches each Floating IP once per reconcile instead of twice, combining the address and current server lookup into a single API call.
- Node watch events now ignore routine kubelet heartbeats and lease renewals, so only gateway-relevant changes trigger a reconcile: Ready condition transitions, candidate or active label changes, and node termination.
- Together these changes cut steady-state API reads from roughly 2,800 per hour to about 120 per hour, leaving headroom on the shared token and preventing rate-limit windows that could delay failover.