feat: allow multiple subscribers on single GVK status updates #5452
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
So far, we haven't had a case where we'd need two separate subscribers to receive channel status update notifications for a single GVK. #5444 introduces a
Watch
inKongUpstreamPolicy
controller that needs to receive status updates ofKongServiceFacade
which already has one subscriber in its controller. This PR mitigates issues that might occur because of multiple subscribers consuming notifications from a single channel by creating a separate channel for everySubscribe
call.Which issue this PR fixes:
Follow up of #5444.