Repository navigation
feat(helm): [NSoC_2026] tighten worker pod egress rules and document required endpoints (#1767) - #1805
Merged
GauravKarakoti merged 1 commit intoNov 16, 2026
Conversation
…required endpoints (GauravKarakoti#1767)
|
@Myparadox-creator is attempting to deploy a commit to the Gaurav's projects Team on Vercel. A member of the Team first needs to authorize it. |
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.
Description
Summary of Changes
Resolves #1767 by hardening the Kubernetes Helm chart deployment configuration with tightened, zero-trust egress rules for backend worker pods and comprehensively documenting required egress destinations in the deployment guides.
Helm Chart Network Policy Updates (
helm/secureflow/templates/networkpolicy.yaml):*-worker-egressNetworkPolicy to support explicitwhitelistedEndpointsentries, allowing operators to configure designated API endpoints (e.g., LLM providers, container registries, VCS APIs) with specific CIDR blocks and destination TCP ports.networkPolicy.enabled: true, external egress is blocked by default; only DNS (kube-dns), same-release PostgreSQL/Redis (when enabled), and explicitly configured endpoints are permitted.secureflow.publicEgressBlock, strictly rejecting dangerous private ranges (10.0.0.0/8,172.16.0.0/12,192.168.0.0/16) and cloud instance metadata addresses (169.254.169.254/32,168.63.129.16/32).extraEgressRulesallowing custom Kubernetes NetworkPolicy egress rule objects (e.g. for private VPC database subnets or proxy gateways).Values & Schema Validation (
helm/secureflow/values.yaml&values.schema.json):networkPolicy.workerEgressinvalues.yamlwithwhitelistedEndpointsandextraEgressRulesproduction examples and documentation comments.values.schema.jsonwith strict schema validation forwhitelistedEndpoints(requiringnameand regex-validated IPv4cidrs, validating destinationportsin range1..65535) andextraEgressRules.Chart Verification Tests (
scripts/test-helm-chart.sh):whitelistedEndpointsrenders destination CIDRs and custom ports accurately in the worker egress NetworkPolicy.0,65536) and missing required fields inwhitelistedEndpointsfail validation.Comprehensive Deployment Guide Documentation (
helm/secureflow/README.md&docs/deployment.md):53)5432)6379,6380)443)443,8443)443)443)production-values.yamlsnippet to demonstrate a fully hardened enterprise deployment.docs/deployment.mdand linked it fromREADME.md.Changeset:
.changeset/worker-egress-hardening-1767.md.PR Checklist
[NSoC_2026]tag requirement