Skip to content

Error in rendering in HTTPRouteRule section #3735

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
Quiwy opened this issue Apr 7, 2025 · 3 comments · May be fixed by #3742
Open

Error in rendering in HTTPRouteRule section #3735

Quiwy opened this issue Apr 7, 2025 · 3 comments · May be fixed by #3742
Assignees
@anshuman-agarwala
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. kind/documentation Categorizes issue or PR as related to documentation. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone
v1.4.0

Comments

@Quiwy
Copy link

Quiwy commented Apr 7, 2025

HTTPRouteMatch example is not rendered well.

Image
@Quiwy Quiwy added the kind/documentation Categorizes issue or PR as related to documentation. label Apr 7, 2025
@shaneutt shaneutt added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Apr 7, 2025
@shaneutt shaneutt moved this to Triage in Gateway API Pipeline Apr 7, 2025
@robscott
Copy link
Member

robscott commented Apr 7, 2025

Thanks for catching this @Quiwy!

/triage accepted
/help

@k8s-ci-robot
Copy link
Contributor

@robscott:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

Thanks for catching this @Quiwy!

/triage accepted
/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Apr 7, 2025
@shaneutt shaneutt moved this from Triage to Next in Gateway API Pipeline Apr 7, 2025
@anshuman-agarwala
Copy link

/assign

@shaneutt shaneutt moved this from Next to In Progress in Gateway API Pipeline Apr 8, 2025
@shaneutt shaneutt added this to the v1.4.0 milestone Apr 8, 2025
@anshuman-agarwala anshuman-agarwala linked a pull request Apr 10, 2025 that will close this issue
Open
@shaneutt shaneutt moved this to In Progress in Release v1.4.0 Apr 22, 2025
@shaneutt shaneutt added kind/bug Categorizes issue or PR as related to a bug. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@anshuman-agarwala anshuman-agarwala

Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. kind/documentation Categorizes issue or PR as related to documentation. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Release v1.4.0
Status: In Progress
Gateway API Pipeline
Status: In Progress
Milestone
v1.4.0
Development

Successfully merging a pull request may close this issue.

fixed doc rendering issues anshuman-agarwala/gateway-api
5 participants
@robscott @shaneutt @Quiwy @k8s-ci-robot @anshuman-agarwala