Investigate running the gateway API conformance tests against the hub gateway

[pmccarthy]

What

Read https://gateway-api.sigs.k8s.io/concepts/conformance/#3-conformance-tests

GWAPI version is currently 0.6.1

Attempt to execute these against a hub defined gateway

Done

• Tests executed fully (failures are fine)
• Document / provide script so that anyone can execute them

[maksymvavilov]

Results https://docs.google.com/document/d/1NxDioky-61FXYmelSTnbxTkiKPH84d6bx0f7mcgZjIU/edit?usp=sharing

[maksymvavilov]

The short description of results: tests should be modified (there is a commit in my fork of gw API with all the modifications) but they still fail at the very first real check - we don't have conditions on our listeners and this promts fails on all the tests for the "base" aka Gateway subset of tests.

[laurafitzgerald]

@makslion out of interest moreso what triggered the change sed 's/gateway-conformance/gw-conf/' in the above commit? It seems to be the bulk of the changes there.

[maksymvavilov]

@makslion out of interest moreso what triggered the change sed 's/gateway-conformance/gw-conf/' in the above commit? It seems to be the bulk of the changes there.

This is how we create manifestwork name and it end up being a label here . There is a limit for character length for labels and using a "long" namespace were exceeding that every time. I'm still cathing specific gateways created by suite that exceeds 63 characters

[maksymvavilov]

Note that conformance tests are a bit funky right now. There is a GEP about it, so, hopefully, it will be a more pleasant experience running them.

[maksymvavilov]

closing this issue. Seems like people are satisfied with the investigation that was done and the first "follow-up" issue was created.