Add Gateway API e2e test using envoy-gateway#955
Conversation
|
Out of curiosity: Do we need both |
|
hey @njuettner No, we don't need the old hello test, I still need to cleanup and fix a few things. |
b89edca to
2c37014
Compare
|
/run cluster-test-suites TARGET_SUITES=./providers/capa/standard |
|
Important Some test suites failed. See the Checks tab for detailed results per suite. Re-run only the failed tests: |
|
/run cluster-test-suites TARGET_SUITES=./providers/capa/standard |
|
Important Some test suites failed. See the Checks tab for detailed results per suite. Re-run only the failed tests: |
f44eaa5 to
16c8c1e
Compare
|
/run cluster-test-suites TARGET_SUITES=./providers/capa/standard |
b2776c9 to
914e57b
Compare
|
/run cluster-test-suites TARGET_SUITES=./providers/capa/standard |
|
Important Some test suites failed. See the Checks tab for detailed results per suite. Re-run only the failed tests: |
|
/run cluster-test-suites TARGET_SUITES=./providers/capa/standard |
|
Important Some test suites failed. See the Checks tab for detailed results per suite. Re-run only the failed tests: |
|
/run cluster-test-suites TARGET_SUITES=./providers/capa/standard |
1 similar comment
|
/run cluster-test-suites TARGET_SUITES=./providers/capa/standard |
|
Important Some test suites failed. See the Checks tab for detailed results per suite. Re-run only the failed tests: |
3f27297 to
594a1a2
Compare
|
/run cluster-test-suites TARGET_SUITES=./providers/capa/standard |
|
/run cluster-test-suites |
ubergesundheit
left a comment
There was a problem hiding this comment.
In case the tests are failing because hello-world-app in latest version is failing to be installed because of values schema mismatch, explicitly use its latest 2.x.x version 2.11.0 which does not have the strict schema..
an update to ensureTestOCIRepository may be required to explicitly set the version
|
Important Some test suites failed. See the Checks tab for detailed results per suite. Re-run only the failed tests: |
Adds a new 'hello world via gateway api' test alongside the existing ingress-nginx test. The new test deploys aws-load-balancer-controller-bundle (CAPA only, optional), gateway-api-bundle, and hello-world configured with an HTTPRoute instead of an Ingress. Includes certificate readiness validation in envoy-gateway-system before deploying hello-world. GatewayAPISupported defaults to true; set to false for capz, capv, capvcd, and eks providers where it is not yet supported.
Signed-off-by: Matias Charriere <matias@giantswarm.io>
Replaces the App-based deployment with the same HelmRelease+OCIRepository approach used in the ingress hello-world test.
Adds the managementCluster.name field to all capa aws-lb-controller-bundle values files, sourced from the MC cluster name via ExtraValues.Installation.
Signed-off-by: Matias Charriere <matias@giantswarm.io>
Signed-off-by: Matias Charriere <matias@giantswarm.io>
The clustertest WC client doesn't register Gateway API types, causing "no kind is registered" errors. Switching to unstructured.Unstructured with an explicit GVK bypasses the scheme requirement entirely.
Signed-off-by: Matias Charriere <matias@giantswarm.io>
Signed-off-by: Matias Charriere <matias@giantswarm.io>
…e+OCI Replace App CR deployments (DeployApp + child app waiting) with the same HelmRelease+OCIRepository pattern already used for the hello-world workload.
Signed-off-by: Matias Charriere <matias@giantswarm.io>
db0da35 to
270af6e
Compare
|
IIRC using hello-world v3 with HR+OCIRepo is fine. The schema conflict comes when installed via App CR, because of the catalog values. I just pushed a few changes, moving the gateway-api-bundle and the aws-lb-controller to OCIRepo+HR |
|
/run cluster-test-suites |
|
Important Some test suites failed. See the Checks tab for detailed results per suite. Re-run only the failed tests: |
Summary
hello world via gateway apitest alongside the existing ingress-nginx test.aws-load-balancer-controller-bundle(CAPA only, optional — skipped if values file absent),gateway-api-bundle, andhello-worldconfigured with an HTTPRoute via envoy-gatewayenvoy-gateway-systembefore deploying hello-worldGatewayAPISupporteddefaults totrue; explicitly set tofalsefor capz, capv, capvcd, and eks providersTowards https://github.com/giantswarm/giantswarm/issues/35836