Repository navigation
fix: make default network policy compatible with Cilium dataplane - #216
Merged
Merged
Conversation
Cilium resolves traffic to security identities and its CIDR selectors only match the `world` identity. Azure NPM matched raw addresses, so rules that work today stop matching once the dataplane changes. network-policy.yaml - add namespaceSelector/podSelector peers to both ipBlock rules. They sit inside the existing rules so they inherit the port lists and widen nothing. Without them, Traefik loses access to app pods: the policies do not name the traefik namespace and admit it only through ipBlock 0.0.0.0/0 matching Traefik's pod IP. cilium-network-policy.yaml - new, egress only. Node addresses resolve to the host / remote-node identities, which no ipBlock rule can match, and NPM's implicit pod-to-own-node allow does not carry over. Covers Azure IMDS at 169.254.169.254, which is link-local and resolves to `host`, so toCIDR would not match it. Rendered under the same switch as the NetworkPolicy. Also adds port 8443 alongside the long-standing 8433 typo in the external egress rule, and drops the unused redisCidr value. Tests reworked to match rules by content rather than list position, so adding a peer or a port no longer breaks every assertion below it. Requires the cilium.io/v2 CRD, so this chart version must only be consumed by clusters already running Azure CNI powered by Cilium. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Keeps this branch to charts/core and charts/dotnet-core only, so the backward compatibility of the network policy change can be tested against an Azure NPM cluster without dragging every consumer chart along. The app-reverse-proxy, cron-job, event-worker and job bumps - version increments plus removal of the unused redisCidr value - are held in a local stash and will be reapplied once core is verified. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…feat/cilium-readiness
mskwierczynski982
marked this pull request as ready for review
September 9, 2026 13:41
LukaszEV
approved these changes
Sep 11, 2026
Merged
8 of 14 tasks
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.
What
Adds
namespaceSelector: {}/podSelector: {}peers to the twoipBlockrules innetwork-policy.yaml. They sit inside the existing rules, so they inherit those rules' ports.+12 lines, nothing removed. Also drops the unused
redisCidrvalue from consumer charts and bumps chart versions.Why
Cilium never matches Pod IPs through
ipBlock:Our policies don't name the
traefiknamespace — they admit Traefik only because0.0.0.0/0matches its pod IP. Under Cilium that stops working and every Traefik-routed app loses ingress.Safe to deploy on NPM now
Under NPM the added peers grant nothing new, since
0.0.0.0/0already covers pod IPs. Renderedmastervs branch with identical values:Description
Briefly describe the problem and solution. Please remember to create 1 PR per 1 chart in case of dependency between them, otherwise PR gate will fail.
Chart
Select the chart that you are modifying:
Checklist
${CHART}/tests/*.py