document GatewayAPI example with xkcd application #1040
Merged
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
Signed-off-by: Jan Wozniak <wozniak.jan@gmail.com>
wozniakjan
force-pushed
the
gatewayapi_example
branch
from
b28501d
to
1aa5d36
Compare
|
Nice improvement! |
that is a good point, ok if I tackle that in a standalone PR? |
JorTurFer
approved these changes
May 27, 2024
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.
This PR documents additional steps to try http-add-on along with GatewayAPI, similar to how
Igresssetup is documented.The selected GatewayAPI implementation Envoy Gateway is stable and well adopted by the community, which should complement the
Ingressdocumentation withnginx-ingress. TheHTTPRouteinterceptor network path is very similar to theIngressinterceptor path.Checklist
see also: #33