Skip to content

feat(networkpolicy): allow vtom-server egress to off-cluster agents (v0.2.6)#10

Merged
cadolbeau-absyss merged 1 commit into
mainfrom
feat/server-external-agent-egress
Jun 18, 2026
Merged

feat(networkpolicy): allow vtom-server egress to off-cluster agents (v0.2.6)#10
cadolbeau-absyss merged 1 commit into
mainfrom
feat/server-external-agent-egress

Conversation

@Cadolbeau

Copy link
Copy Markdown
Contributor

Summary

  • Adds serverExternalAgentEgress — a configurable list of ipBlock egress rules on vtom-server, enabling it to reach on-premise or remote agents (ports 30014 sbdaemon, 30010) via VPN or VPC peering
  • The rule allow-egress-server-to-external-agents is only rendered when the list is non-empty → no impact on existing deployments
  • Follows the same pattern as the existing apiserverExternalEgress

Usage

vtom:
  serverExternalAgentEgress:
    - port: 30014
      protocol: TCP
      cidr: "10.20.5.0/24"   # subnet of the external agents
    - port: 30010
      protocol: TCP
      cidr: "10.20.5.0/24"

Test plan

  • helm lint passes on all 4 cloud profiles (azure, aws, gcp, onpremise)
  • helm template with serverExternalAgentEgress populated renders the allow-egress-server-to-external-agents NetworkPolicy
  • helm template without the key (empty list) renders no extra NetworkPolicy

…v0.2.6)

Add serverExternalAgentEgress — a configurable list of ipBlock rules that
let vtom-server reach on-premise or remote agents (ports 30014/30010) via
VPN or VPC peering. Follows the same pattern as apiserverExternalEgress.
The rule is only rendered when the list is non-empty, so existing deployments
are unaffected.

@cadolbeau-absyss cadolbeau-absyss left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

@cadolbeau-absyss cadolbeau-absyss merged commit edaa13c into main Jun 18, 2026
4 checks passed
@cadolbeau-absyss cadolbeau-absyss deleted the feat/server-external-agent-egress branch June 18, 2026 10:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants