Skip to content

Adds HTTPRouting User Doc#558

Merged
danehans merged 1 commit intoenvoyproxy:mainfrom
danehans:http_routing_doc
Oct 17, 2022
Merged

Adds HTTPRouting User Doc#558
danehans merged 1 commit intoenvoyproxy:mainfrom
danehans:http_routing_doc

Conversation

@danehans
Copy link
Copy Markdown
Contributor

xref: #501

Signed-off-by: danehans daneyonhansen@gmail.com

@danehans danehans requested a review from a team as a code owner October 13, 2022 16:03
@danehans danehans marked this pull request as draft October 13, 2022 16:12
@danehans danehans added the documentation Improvements or additions to documentation label Oct 13, 2022
@danehans danehans added this to the 0.2.0 milestone Oct 13, 2022
@fredgineer
Copy link
Copy Markdown
Contributor

Cannot properly replicate arm issues on my m1 mac now, likely due to rosetta. Will run another round of tests on the pis after the weekend.

@danehans should this PR also update the quickstart with the k8s-staging-ingressconformance/echoserver, replacing httpbin?

Signed-off-by: danehans <daneyonhansen@gmail.com>
@danehans
Copy link
Copy Markdown
Contributor Author

@danehans should this PR also update the quickstart with the k8s-staging-ingressconformance/echoserver, replacing httpbin?

@fredzach I want to keep this PR focused on the HTTP routing user doc changes. Would you like to submit a PR for updating the Quickstart image?

@danehans
Copy link
Copy Markdown
Contributor Author

Removing "Draft" since #571 adds .md support.

@danehans danehans marked this pull request as ready for review October 15, 2022 18:54
Copy link
Copy Markdown
Contributor

@arkodg arkodg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

Copy link
Copy Markdown
Contributor

@youngnick youngnick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with one minor formtting nit.

an HTTPRoute must be configured with `parentRefs` which reference the parent Gateway(s) that it should be attached to.
An HTTPRoute can match against a [single set of hostnames][spec]. These hostnames are matched before any other matching
within the HTTPRoute takes place. Since `example.com`, `foo.example.com`, and `bar.example.com` are separate hosts with
different routing requirements, each is deployed as its own HTTPRoute - `example-route, ``foo-route`, and `bar-route`.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
different routing requirements, each is deployed as its own HTTPRoute - `example-route, ``foo-route`, and `bar-route`.
different routing requirements, each is deployed as its own HTTPRoute - `example-route`, `foo-route`, and `bar-route`.

@danehans
Copy link
Copy Markdown
Contributor Author

@youngnick merging since the PR is already approved and I'll resolve your feedback shortly in a follow-on PR.

@danehans danehans merged commit 5e3db60 into envoyproxy:main Oct 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants