This repository has been archived by the owner on Jul 11, 2023. It is now read-only.
envoy/permissive-mode: use cluster service discovery and routing #1450
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
…ting When operating in permissive traffic policy mode, OSM relies on native kubernetes networking to route traffic to services. Since Kubernetes is already aware of how to discover and route traffic to services, rely on this instead of the control plane to explicitly program and discover endpoints. This change makes the controller logic simpler for permissive mode and is an optimization over the current implementation. Resolves openservicemesh#1403
shashankram
changed the title
snehachhabria
approved these changes
Aug 7, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When operating in permissive traffic policy mode, OSM relies on native
kubernetes networking to route traffic to services. Since Kubernetes
is already aware of how to discover and route traffic to services,
rely on this instead of the control plane to explicitly program and
discover endpoints. This change makes the controller logic simpler for
permissive mode and is an optimization over the current implementation.
The change also moves the ListenerFilters in the outbound listener to the
mesh filter chain since the mesh traffic requires them as well, and removes
the unused TlsInspector filter.
Resolves #1403
Please answer the following questions with yes/no.
no(If so, did you notify the maintainers and provide attribution? )