docs(blog): add internal load balancer example for approuting-istio Gateway API#5751
Open
rkasture wants to merge 4 commits intoAzure:masterfrom
Open
docs(blog): add internal load balancer example for approuting-istio Gateway API#5751rkasture wants to merge 4 commits intoAzure:masterfrom
rkasture wants to merge 4 commits intoAzure:masterfrom
Conversation
…ateway API Add a new 'Internal load balancer' section to the app routing Gateway API blog post showing how to configure an internal (private) Gateway using spec.infrastructure.annotations with Azure load balancer annotations. Includes: - Complete Gateway YAML with internal LB and subnet annotations - Commands to verify the internal IP assignment - Links to networking prerequisites and annotation reference docs Closes Azure#5748 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds documentation to the existing app routing Gateway API blog post to help readers configure an internal (private) Azure Load Balancer for an approuting-istio Gateway by using spec.infrastructure.annotations.
Changes:
- Adds an Internal load balancer subsection with a Gateway YAML example that sets internal LB annotations.
- Adds verification commands to confirm the Gateway is programmed and returns a private IP in
status.addresses. - Adds links to AKS internal load balancer prerequisites and the Azure Load Balancer annotations reference.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Author
|
@copilot apply changes based on the comments in this thread |
| AKS propagates these annotations onto the Kubernetes Service it creates for the Gateway. After the Gateway is programmed, its `status.addresses` will contain a private IP from the specified subnet (or the cluster's default subnet if the subnet annotation is omitted): | ||
|
|
||
| ```bash | ||
| kubectl wait --for=condition=programmed gateways.gateway.networking.k8s.io httpbin-gateway --timeout=120s |
There was a problem hiding this comment.
Gateway API’s standard condition type is Programmed (capital P). Using condition=programmed may fail to match the condition on some clusters/kubectl versions. Recommend updating the command to wait for condition=Programmed to ensure it reliably works.
Suggested change
| kubectl wait --for=condition=programmed gateways.gateway.networking.k8s.io httpbin-gateway --timeout=120s | |
| kubectl wait --for=condition=Programmed gateways.gateway.networking.k8s.io httpbin-gateway --timeout=120s |
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
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.
Summary
Adds a new Internal load balancer section to the app routing Gateway API blog post showing how to configure a private (internal) Gateway using \spec.infrastructure.annotations.
What's included
Motivation
Closes #5748 — users migrating from NGINX app routing to \�pprouting-istio\ need documented examples for creating internal load balancers on dedicated subnets. The existing blog post only shows the external (public) Gateway pattern.
Validation
pm run build\ succeeds (broken anchors in output are pre-existing, unrelated to this change)