Summary
A Gateway listener with an unverified hostname is dropped. The operator sets Programmed to false, skips the downstream write, and requeues immediately. The status it writes is already correct, so nothing changes and the requeue repeats. There is no backoff.
Impact
Nine production gateways write status about once per second, roughly 966,000 writes per day. Each write is stored at RequestResponse with both bodies and triggers an API server admission read. This is about a fifth of all platform audit events and more than half the bytes stored.
Evidence
Over seven days: 3.4 million Gateway status updates against 792 reads. The affected gateways hold the same resourceVersion, generation and status hash across the entire window. One gateway took 53 consecutive updates in 92 seconds under a single resourceVersion.
The trigger is a listener reporting UnverifiedHostnamesPresent. That condition clears only when the domain is verified, so the retry has nothing to converge on.
Introduced in v0.26.0. Still present in v0.26.1.
Success looks like
- Status is not written when the computed status matches the observed status
- A condition that cannot resolve without user action backs off instead of retrying at reconcile speed
Summary
A Gateway listener with an unverified hostname is dropped. The operator sets Programmed to false, skips the downstream write, and requeues immediately. The status it writes is already correct, so nothing changes and the requeue repeats. There is no backoff.
Impact
Nine production gateways write status about once per second, roughly 966,000 writes per day. Each write is stored at RequestResponse with both bodies and triggers an API server admission read. This is about a fifth of all platform audit events and more than half the bytes stored.
Evidence
Over seven days: 3.4 million Gateway status updates against 792 reads. The affected gateways hold the same resourceVersion, generation and status hash across the entire window. One gateway took 53 consecutive updates in 92 seconds under a single resourceVersion.
The trigger is a listener reporting UnverifiedHostnamesPresent. That condition clears only when the domain is verified, so the retry has nothing to converge on.
Introduced in v0.26.0. Still present in v0.26.1.
Success looks like