Remove egress restriction from generated NetworkPolicy#17
Merged
glours merged 1 commit intodocker:mainfrom Apr 14, 2026
Merged
Conversation
The NetworkPolicy template was restricting both ingress and egress to pods within the same Compose network. This incorrectly blocks DNS resolution (CoreDNS) and any outbound traffic to external services, the host, or non-Compose pods (e.g. telepresence traffic-manager). Docker Compose's network model only restricts which services can reach each other (ingress), not where they can send traffic. Pods on a Compose network can freely reach DNS, the internet, and the host. This was previously invisible because common CNIs (Docker Desktop's vpnkit, older kindnet) did not enforce NetworkPolicies. kind v1.34.3+ now ships kindnet with kube-network-policies enabled, making the overly restrictive policy actively break DNS and inter-service communication. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
ndeloof
approved these changes
Apr 14, 2026
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
2 participants
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.
The NetworkPolicy template was restricting both ingress and egress to pods within the same Compose network. This incorrectly blocks DNS resolution (CoreDNS) and any outbound traffic to external services, the host, or non-Compose pods (e.g. telepresence traffic-manager).
Docker Compose's network model only restricts which services can reach each other (ingress), not where they can send traffic. Pods on a Compose network can freely reach DNS, the internet, and the host.
This was previously invisible because common CNIs (Docker Desktop's vpnkit, older kindnet) did not enforce NetworkPolicies. kind v1.34.3+ now ships kindnet with kube-network-policies enabled, making the overly restrictive policy actively break DNS and inter-service communication.