Tests/run conformance tests

[vepatel]

Proposed changes

Write a clear and concise description that helps reviewers understand the purpose and impact of your changes. Use the
following format:

Problem: Ability to run gateway api conformance tests locally on KinD cluster.

Solution: Run tests in a container with the help of provided make commands.

Testing: Build the test runner image and execute tests

Please focus on (optional): If you any specific areas where you would like reviewers to focus their attention or provide
specific feedback, add them here.

Closes #648

Checklist

Before creating a PR, run through this checklist and mark each as complete.

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have checked that all unit tests pass after adding my changes
• I have updated necessary documentation
• I have rebased my branch onto main
• I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

[vepatel]

in-progress, seems like there's an issue with provisioner. @pleshakov is taking a look to confirm.

[pleshakov]

{“level”:“info”,“ts”:“2023-06-05T17:26:04Z”,“logger”:“eventLoop”,“msg”:“added an event to the next batch”,“type”:“*events.UpsertEvent”,“total”:1}
panic: failed to create deployment: Deployment.apps “nginx-gateway-gateway-conformance-infra-same-namespace-with-http-listener-on-8080" is invalid: [spec.selector.matchLabels: Invalid value: “nginx-gateway-gateway-conformance-infra-same-namespace-with-http-listener-on-8080”: must be no more than 63 characters, spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{“app”:“nginx-gateway-gateway-conformance-infra-same-namespace-with-http-listener-on-8080”}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: invalid label selector]

when creating a deployment, the generated labels are too long -- I will prepare a fix

[pleshakov]

Added a different bug -- #714 -- which is also a blocker

This one prevented one of base Gateways to become Programmed in the status, because NGINX will fail to reload.

[pleshakov]

hi @vepatel
I found a few issues. but looks good otherwise

[pleshakov]

👍