Repository navigation
feat: add Traefik egress access to network policies - #165
Open
aperolschpritz wants to merge 1 commit into
Open
aperolschpritz wants to merge 1 commit into
aperolschpritz wants to merge 1 commit into
Conversation
Add an independent allowTraefikAccess flag to App and Agent network policies so workloads can reach other apps and agents through their exposed Traefik domains even when internet egress is disabled. The flag defaults to false and adds an egress rule for the Traefik pods without port restrictions.
This branch has not been deployed
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
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.
Summary
Add an independent Traefik Access egress flag to App and Agent network policies. It lets a workload reach other Apps and Agents through their exposed Traefik Domains even when general internet egress is disabled.
Traefik Accesstoggle in the Egress section.Allow Traefik accesstoggle on the Network Policy card.false.0016-traefik-access-egress.md.The rule targets the Traefik pods without ports because the k3s Traefik pods listen on
8000/8443; restricting to80/443would miss the translated pod port. Internet access stays unchanged and still excludes private CIDRs.Evidence
Verification:
git.service.unit.spec.tsbecause no container runtime is available.tsc --noEmit: no new errors.Deploy note: run
yarn prisma-deploy. Existing workloads keep the previous isolation; Traefik access is opt-in per App or Agent.Merge Danger
Door: two-way
The migration only adds boolean columns with
false, so existing workloads keep their current behavior. Reverting the code leaves the unused columns harmless.Blast Radius: network-policy
Changes the egress rules only for workloads where the new flag is explicitly enabled. API changes are additive.