Root cause: The status updater has been added as a Runnable in the controller manager, and started after the controller started watching resources. If a resource change comes before the status updater is started, the status will be discarded. This only happens when EG is just started.
When upgrading Gateway API to v1.2.0, I discovered that the status updates were being discarded by the status updater, which caused the upgrade test to fail waiting for the HTTPRoute to be accepted.
Root cause: The status updater has been added as a Runnable in the controller manager, and started after the controller started watching resources. If a resource change comes before the status updater is started, the status will be discarded. This only happens when EG is just started.
Test log:
HTTPRoute, status was not updated.
Failed tests:
probably related to https://github.com/envoyproxy/gateway/issues/4264