Repository navigation
Add Egress policy docs to your first MCP tools - #640
Closed
Stevenjin8 wants to merge 1 commit into
Closed
Stevenjin8 wants to merge 1 commit into
Stevenjin8 wants to merge 1 commit into
Conversation
Signed-off-by: Steven Jin <steven.jin@solo.io>
Stevenjin8
force-pushed
the
copilot/document-tool-server-egress
branch
from
October 20, 2026 20:54
ab501ac to
5e8bd73
Compare
Author
|
closing, i tried this in master an a subtrate egress policy gets automatically created. |
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.
We get DNS errors in the demo because we need to explicitly create EgressPolicy.
I kinda wish there was a way to express "allow everything" for egress. Horrible in prod, but very nice for demos since users can apply it at the very start and not have to keep so many crds in mind.