fix(chart): select agent pods by stable managed-by label; add connect… - #13
Merged
Merged
Conversation
DominikPinsel
force-pushed
the
fix/netpol-stable-agent-selectors
branch
from
August 6, 2026 13:32
503976a to
d3fa7d7
Compare
…ebhook-ingress The chart's NetworkPolicies selected agent pods with app.kubernetes.io/component: agents, but Deployments created by earlier operator versions carry an immutable selector without that label; until the preserve-selector fix reconciles them, their pods lack the label and are silently isolated from hub-backend/qdrant under default-deny (or drop out of the agent-egress lockdown). Keep component: agents as the sole agent selector: it is the semantic identity label and stays precise if the agent-operator later manages other workload types (which will carry their own component value), whereas selecting by managed-by would grant agent privileges to any operator-managed pod. Document the migration prerequisite: deploy this chart only after an operator version with the preserve-selector fix has reconciled all agents (it keeps their immutable selector and relabels rolled-out pods with component: agents), plus a one-liner to verify no agent pod is missing the label. Also add a connectors-webhook-ingress policy: connector receiver pods are created dynamically by the event-source-gateway operator, and webhook producers must be able to reach them under default-deny. The ingress controller's namespace is always allowed (external webhooks), and in-cluster producers that deliver directly (e.g. a Forgejo running in the same cluster) can be added via the new networkPolicy.connectorWebhookSources value.
DominikPinsel
force-pushed
the
fix/netpol-stable-agent-selectors
branch
from
August 6, 2026 13:58
d3fa7d7 to
de37efa
Compare
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.
…ors-webhook-ingress
The chart's NetworkPolicies selected agent pods with app.kubernetes.io/component: agents. That label was only added to the agent-operator's label set recently; Deployments created by earlier operator versions carry an immutable selector without it and could not be relabelled, so their pods never matched the policies and were silently isolated from hub-backend/qdrant under default-deny.
Select agent pods by app.kubernetes.io/managed-by: agent-operator instead — that label has been part of every agent Deployment's immutable selector since the first operator release, so it is present on every agent pod regardless of operator version. Applies to the hub-backend ingress rule, the qdrant ingress rule, and the agent-egress podSelector.
Also add a connectors-webhook-ingress policy: connector receiver pods are created dynamically by the event-source-gateway operator, and webhook producers must be able to reach them under default-deny. The ingress controller's namespace is always allowed (external webhooks), and in-cluster producers that deliver directly (e.g. a Forgejo running in the same cluster) can be added via the new
networkPolicy.connectorWebhookSources value.
Summary
Type of change
Testing
Related issues