Docs: mention north/south traffic #723
Merged
Conversation
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.
What type of PR is this?
documentation
Which issue does this PR fix:
Connected to, but not fixing, issue 535.
What does this PR do / Why do we need it:
If any kubernetes users discover this project (which seems to be "an implementation of the Kubernetes Gateway API"), it could be really helpful to discuss the topic from issue 535. Gateway API is meant to be v2 of Ingress API, which is usually applied to north/south traffic. It takes time to understand that VPC Lattice is something else.
(Open to editing/wording changes).
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.