Update previous API gateway tutorials to bring into parity (v2) #1238
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
nijikokun
reviewed
Apr 14, 2025
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.
Closing #1192 in favor of this PR, as I took a completely different take on how to organize them after learning a lot from the multicloud one.
This looks like a ton of change, but it's a lot of copy-paste to makes sure that all three API gateway specific tutorials follow the same pattern of implementation (as lead by the multicloud tutorial), use the same demo services, and, for the K8s ones, use the new Operator features like
AgentEndpointresources, instead of Gateway API (which requires way more complicated YAML configs).@shubcodes You might be helpful with your experience in these kinds of setups.
@Alice-Lilith Would love to make sure I'm representing the K8s features properly—I've tested these to work, but I'm sure there are even better ways to present the workflows and make it super smooth.