The committers listed above are authorized under a signed CLA.

• ✅ login: aharbis / name: Aidan Harbison (75f87dd)

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Welcome @aharbis!

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. 😃

Hi @aharbis. 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.

Working with corporate to get the CLA sorted.

CLA should be all set.

@robscott @howardjohn are you able to review this PR? Please let me know if it's missing anything.

We can merge this PR, but without a submitted conformance test, when I perform the implementation page review after v1.4, the implementation will be moved to the "Stale" designation during that review. The implementations page now includes some information about these reviews, what they entail, and when they will be done. tl;dr after reach release, we'll review the page and reclassify implementations into three states:

• Conformant - has a recent, passing conformance report for all claimed features
• Partially conformant - has a recent conformance report for at least some of the claimed features
• Stale - does not meet the criteria for the other states.

The Stale category and all entries will be removed in the v1.5 review, so only implementations that have submitted a recent conformance report will be listed on the page at that time.

How far is your implementation along? Any chance you will be able to get at least a partial conformance review in in the next couple of months? (Even one that only passes a single HTTPRoute check would do).