Add egress and route options to container network config#826
Merged
mattoni merged 4 commits intoJun 22, 2026
Merged
Conversation
blewisCycle
reviewed
Jun 22, 2026
blewisCycle
reviewed
Jun 22, 2026
blewisCycle
approved these changes
Jun 22, 2026
…s-to-container-config-in-api-spec
mattoni
deleted the
mattoni/eng-4608-add-egress-and-route-options-to-container-config-in-api-spec
branch
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.
Adds two new options to the container network config
egress_via_gateway: Routes traffic from the container out to the environment's gateway service, operating the same as a virtual machine in the same environment.routes: Custom network routes, where you can match CIDRs and forward that traffic to a target gateway. This allows for very advanced network options like utilizing VPNs within an environment for outbound traffic.