You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When enabled, a `NetworkPolicy` is applied to the workflow namespace (`global.backendNamespace`) that allows unrestricted external internet egress while blocking cross-namespace cluster traffic except to explicitly allowlisted namespaces.
52
54
53
55
| Parameter | Description | Default |
54
56
|-----------|-------------|---------|
55
-
|`global.network.restrictEgress`| Restrict egress traffic for workflow pods |`false`|
|`global.network.allowlistEgress.additionalVolumes`| Additional volumes for sidecar containers |`[]`|
62
-
|`global.network.allowlistEgress.hostAliases`| Host aliases for pods |`[]`|
63
-
|`global.network.allowlistEgress.resources.requests.cpu`| CPU requests for allowlist squid proxy server |`2`|
64
-
|`global.network.allowlistEgress.resources.requests.memory`| Memory requests for allowlist squid proxy server |`4Gi`|
65
-
|`global.network.allowlistEgress.resources.limits.memory`| Memory limits for allowlist squid proxy server |`4Gi`|
57
+
|`global.networkPolicy.enabled`| Create the `NetworkPolicy`. When `false`, all egress is unrestricted. |`false`|
58
+
|`global.networkPolicy.clusterCIDRs`| Internal cluster CIDRs (pod CIDR, service CIDR) to exclude from the external egress rule. Required for namespace isolation to be effective. |`[]`|
59
+
|`global.networkPolicy.dnsNamespace`| Namespace containing the cluster DNS service (CoreDNS/kube-dns). Port 53 egress is allowed to pods in this namespace. |`kube-system`|
60
+
|`global.networkPolicy.allowedNamespaces`| Additional namespaces that workflow pods may reach. |`[]`|
61
+
|`global.networkPolicy.additionalEgressRules`| Raw `NetworkPolicyEgressRule` objects appended to the policy. Use for IP-based allowances or DNS workarounds on iptables-based CNIs. |`[]`|
66
62
67
63
68
64
### Global Logging Settings
@@ -198,5 +194,5 @@ This chart requires:
198
194
- Each component can be configured independently with custom resources and settings
199
195
- Includes comprehensive mount monitoring with failure threshold configuration
200
196
- Integrates with OpenTelemetry for observability
201
-
- Configurable network egress controls for security
197
+
- Optional Kubernetes `NetworkPolicy` to restrict cross-namespace egress while permitting external internet traffic
202
198
- Priority classes for workload scheduling optimization
0 commit comments