in mesh upstreams #10080
Open
in mesh upstreams #10080
+82
−39
Conversation
This file contains 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
stevenctl
force-pushed
the
mesh-upstream-api
branch
from
ab6135e
to
eafcdc8
Compare
artberger
reviewed
Sep 23, 2024
Co-authored-by: Art <artberger@users.noreply.github.com>
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
To support gloo-gateway as a mesh ingress, we need a mechanism to reference the VirtualDestination. The hosts field of a static upstream marked for mesh will use ServiceEntry (which in this usecase are expected to be generated by VD) to find the endpoints we want to route to.
API changes
inMeshbool marker to Upstream_StaticCode changes