Skip to content

docs: add end-to-end ingress setup guide#681

Open
Aaravanand00 wants to merge 1 commit intokgateway-dev:mainfrom
Aaravanand00:enhance/end-to-end-ingress-guide
Open

docs: add end-to-end ingress setup guide#681
Aaravanand00 wants to merge 1 commit intokgateway-dev:mainfrom
Aaravanand00:enhance/end-to-end-ingress-guide

Conversation

@Aaravanand00
Copy link
Copy Markdown

This PR adds a step-by-step End-to-End Ingress Setup guide to the documentation site.

The guide walks through deploying a sample application, configuring a Gateway and HTTPRoute, enabling path-based routing, and securing traffic with TLS — all within a single namespace model.

It follows existing documentation structure and shortcodes, and does not introduce any runtime changes.

Signed-off-by: Aarav Anand <aaravanand5749@gmail.com>
@Aaravanand00 Aaravanand00 force-pushed the enhance/end-to-end-ingress-guide branch from d323e57 to 23ea5fe Compare March 2, 2026 12:52
@Aaravanand00
Copy link
Copy Markdown
Author

Hi @npolshakova mam,

Following your earlier feedback, I’ve moved the End-to-End Ingress guide to the kgateway.dev repository and aligned it with the existing documentation structure (frontmatter, shortcodes, sidebar positioning, and relative links).

The guide demonstrates a single-namespace ingress setup covering Gateway, HTTPRoute, path-based routing, and TLS, and is focused on onboarding clarity.

This continues the work originally proposed in kgateway-dev/kgateway#13399, now submitted in the correct repository.

Would appreciate your review and any suggestions for further improvements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant