You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of now, the listener status is initialized only when the gateway is not ready yet; in this case, all the listeners are set with the proper status, and the gateway resource is updated. This approach that we currently have led to not reconciling the correct listener status whenever it changes and having an inappropriate gateway status under some circumstances, such as whenever a listener is not ready anymore because of a ReferenceGrant missing or malformed (introduced in #2774).
Proposed Solution
At every gateway reconciliation loop, we should compute the expected gateway status and compare it to the actual one; if they differ, the gateway resource should be updated, no matter if the gateway is ready.
Additional information
This issue should be solved after #2694, because treating the gateway status as a snapshot instead of a ledger, will help a lot to structure the code properly.
Acceptance Criteria
Every time some event that triggers gateway reconciliation happens, the expected gateway status should be enforced on the gateway resource.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Problem Statement
As of now, the listener status is initialized only when the gateway is not ready yet; in this case, all the listeners are set with the proper status, and the gateway resource is updated. This approach that we currently have led to not reconciling the correct listener status whenever it changes and having an inappropriate gateway status under some circumstances, such as whenever a listener is not ready anymore because of a
ReferenceGrant
missing or malformed (introduced in #2774).Proposed Solution
At every gateway reconciliation loop, we should compute the expected gateway status and compare it to the actual one; if they differ, the gateway resource should be updated, no matter if the gateway is ready.
Additional information
This issue should be solved after #2694, because treating the gateway status as a snapshot instead of a ledger, will help a lot to structure the code properly.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: