Skip to content

feat: allow dynamic list of ingress rules - #21

Merged
levkk merged 1 commit into
pgdogdev:mainfrom
siryur:feat/networkpolicy-dynamic-ingress
Aug 18, 2026
Merged

feat: allow dynamic list of ingress rules#21
levkk merged 1 commit into
pgdogdev:mainfrom
siryur:feat/networkpolicy-dynamic-ingress

Conversation

@siryur

@siryur siryur commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

The control NetworkPolicy only ever allowed traffic from the ingress-nginx namespace, with no way to add more. In clusters that deny pod-to-pod traffic by default, that leaves no way to permit other legitimate callers, such as PgDog pods reaching the control plane's API.

Add networkPolicy.extraIngress, a list of NetworkPolicyIngressRule entries appended to the control NetworkPolicy's ingress rules verbatim, alongside the existing ingress-nginx rule.

Fix #20

The control NetworkPolicy only ever allowed traffic from the
ingress-nginx namespace, with no way to add more. In clusters that
deny pod-to-pod traffic by default, that leaves no way to permit
other legitimate callers, such as PgDog pods reaching the control
plane's API.

Add networkPolicy.extraIngress, a list of NetworkPolicyIngressRule
entries appended to the control NetworkPolicy's ingress rules
verbatim, alongside the existing ingress-nginx rule.

@levkk levkk left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙏

@levkk
levkk merged commit a22f01d into pgdogdev:main Aug 18, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow dynamic list of ingress rules

2 participants