docs: add Higress v2.2.4 Gateway API conformance report

[EndlessSeeker]

/kind documentation
/area conformance-test

What type of PR is this?

Adds the generated Higress v2.2.4 Gateway API v1.6.0 standard-channel conformance report and lists Higress as a conformant Gateway implementation.

The submitted GATEWAY-HTTP Core profile result is 37 passed, 0 failed, and 0 skipped. The report is included exactly as generated by the official v1.6.0 suite.

Why is this PR needed?

Higress v2.2.4 includes Gateway API v1.6.0 support and now has release-level conformance evidence using the canonical project identity:

• organization: higress-group
• project: higress
• URL: https://github.com/higress-group/higress

Does this PR introduce a user-facing change?

NONE

Additional documentation

The implementation README contains reproduction steps and links the exact Higress v2.2.4 release. The report SHA-256 is 6d342dd57ed470ea6780643cbe01c94a2e685f5cfb63199504dd50d7f4a11755.

AI assistance disclosure

OpenAI Codex assisted with running the official suite, verifying the generated report, and preparing this submission. The commit is authored and signed off by EndlessSeeker.

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: EndlessSeeker
Once this PR has been reviewed and has the lgtm label, please assign kflynn for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• conformance/OWNERS
• site/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[linux-foundation-easycla]

• ❌ - login: @EndlessSeeker / name: EndlessSeeker. The commit (29fcfce) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

[kubernetes-prow]

Welcome @EndlessSeeker!

It looks like this is your first PR to kubernetes-sigs/gateway-api 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/gateway-api has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[kubernetes-prow]

Hi @EndlessSeeker. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[EndlessSeeker]

Local validation update:

• make wizard-data conformance-data passed and parsed the new report successfully.
• NETLIFY=true make build-docs-netlify passed locally with Hugo v0.165.0.
• npx --yes markdown-link-check conformance/reports/v1.6/higress-group-higress/README.md passed all 3 links.

The Netlify deploy preview failed, but I could not reproduce a content/build failure locally; Netlify public deploy history also shows several unrelated previews failing in the same time window.

[snorwin]

@EndlessSeeker thanks for submitting the conformance report.

To proceed, could you please sign the CLA?

[EndlessSeeker]

/easycla

[EndlessSeeker]

@snorwin, thank you for your guidance and patience. I have submitted the EasyCLA corporate authorization request and am waiting for approval from the relevant CLA manager; if it is still pending next Monday, August 17, I will follow up with them.