Add Gateway API CRDs to controller test data (#340)

Browse Source

The PR #335 is adding controller tests for the HTTP route which means it
needs the CRDs. So simplify future testing work we will vendor the CRDs
from the release inside of the testdata directory. This is setup so that
changes to the GW API version will force generate to be run again.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Chores**
* Updated the generated Gateway API artifacts used in the build pipeline
to ensure the latest `standard-install.yaml` content is bundled.
* Kept the bundled Gateway API version synchronized automatically by
deriving it from the project’s module version and regenerating the asset
when dependencies change.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

...

This commit is contained in:

Philip Laine

2026-06-25 10:45:09 +02:00

committed by GitHub

parent 447bbc76cd

commit 84e9bff602

2 changed files with 17532 additions and 1 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

internal/controller/testdata/crd/gateway-api.yaml

Vendored

+17527

File diff suppressed because it is too large Load Diff