fix(chart): allow webhook connector pods to reach hub-backend under n… - #12
Merged
Merged
Conversation
…etpol Connector webhook-receiver pods (created by the event-source-gateway operator) publish accepted webhooks directly to hub-backend (POST /api/internal/events on hub.port). The hub-backend NetworkPolicy only allowed ingress from hub-frontend, mcp, agents, and the ingress namespace, so under the default-deny posture every publish was refused: senders received '500 publish failed' and no connector events reached the event queue. Add the connector pods (managed-by: connector-operator) to the hub-backend policy's ingress rules and update the network policy inventory doc (policy table, traffic flows, known gaps, troubleshooting symptoms).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
…etpol
Connector webhook-receiver pods (created by the event-source-gateway operator) publish accepted webhooks directly to hub-backend (POST /api/internal/events on hub.port). The hub-backend NetworkPolicy only allowed ingress from hub-frontend, mcp, agents, and the ingress namespace, so under the default-deny posture every publish was refused: senders received '500 publish failed' and no connector events reached the event queue.
Add the connector pods (managed-by: connector-operator) to the hub-backend policy's ingress rules and update the network policy inventory doc (policy table, traffic flows, known gaps, troubleshooting symptoms).
Summary
Type of change
Testing
Related issues