-
Notifications
You must be signed in to change notification settings - Fork 7.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement external (from the mesh to the outside) traffic control #496
Comments
Related issues: |
can you elaborate a bit more on what you propose ? |
@ldemailly Please see design proposal https://goo.gl/94DTSH. Your comments are welcome. |
@ldemailly Please see also #552 . |
This PR ensures that all tools in the bin directory use bazel's version of go. It creates uniformity between bazel build and tests like race, code coverage and perf. Former-commit-id: 953cdab6577934c66f823fdea9d6929c9e22e262
This PR ensures that all tools in the bin directory use bazel's version of go. It creates uniformity between bazel build and tests like race, code coverage and perf. Former-commit-id: 4231bb8b7635f1dd6cb0f0066260292561da4e38
* Convert Pilot ip mesh attributes to bytes * Update comment * Update after review comment
* update hub and tag examples * fix lint * update docs * lint * move up grafana to latest * update version * Revert "update version" This reverts commit 5cba0da9f0fdd3ac05ef4de0054872504ae3007a. * update version
Instead of defining external services or IP ranges to be ignored by proxies.
Based on the design proposals https://goo.gl/94DTSH, https://goo.gl/eYY7na.
It includes support of various protocols, and also routing-rules-to-egress-rules, like fault injection, http redirection, http rewrite, etc., when the target is an external (outside of the mesh) service
The text was updated successfully, but these errors were encountered: