Skip to content

Add Gateway API e2e test using envoy-gateway#955

Open
mcharriere wants to merge 12 commits intomainfrom
migrate-envoy
Open

Add Gateway API e2e test using envoy-gateway#955
mcharriere wants to merge 12 commits intomainfrom
migrate-envoy

Conversation

@mcharriere
Copy link
Copy Markdown
Contributor

@mcharriere mcharriere commented Mar 13, 2026

Summary

  • Adds a new hello world via gateway api test alongside the existing ingress-nginx test.
  • Deploys aws-load-balancer-controller-bundle (CAPA only, optional — skipped if values file absent), gateway-api-bundle, and hello-world configured with an HTTPRoute via envoy-gateway
  • Validates certificate readiness in envoy-gateway-system before deploying hello-world
  • GatewayAPISupported defaults to true; explicitly set to false for capz, capv, capvcd, and eks providers

Towards https://github.com/giantswarm/giantswarm/issues/35836

@mcharriere mcharriere requested review from a team as code owners March 13, 2026 08:29
@mcharriere mcharriere marked this pull request as draft March 13, 2026 08:30
@njuettner
Copy link
Copy Markdown
Member

njuettner commented Mar 13, 2026

Out of curiosity:

Do we need both hello world via gateway api test alongside the existing ingress-nginx test ? Or could we actually drop ingress-nginx?

@mcharriere
Copy link
Copy Markdown
Contributor Author

hey @njuettner

No, we don't need the old hello test, I still need to cleanup and fix a few things.
Please consider this WIP, I just switched it to draft.

@mcharriere
Copy link
Copy Markdown
Contributor Author

/run cluster-test-suites TARGET_SUITES=./providers/capa/standard

@tinkerers-ci
Copy link
Copy Markdown

tinkerers-ci bot commented Mar 13, 2026

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

@mcharriere
Copy link
Copy Markdown
Contributor Author

/run cluster-test-suites TARGET_SUITES=./providers/capa/standard

@tinkerers-ci
Copy link
Copy Markdown

tinkerers-ci bot commented Mar 13, 2026

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

@mcharriere
Copy link
Copy Markdown
Contributor Author

/run cluster-test-suites TARGET_SUITES=./providers/capa/standard

@mcharriere
Copy link
Copy Markdown
Contributor Author

/run cluster-test-suites TARGET_SUITES=./providers/capa/standard

@tinkerers-ci
Copy link
Copy Markdown

tinkerers-ci bot commented Apr 13, 2026

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

@mcharriere
Copy link
Copy Markdown
Contributor Author

/run cluster-test-suites TARGET_SUITES=./providers/capa/standard

@tinkerers-ci
Copy link
Copy Markdown

tinkerers-ci bot commented Apr 14, 2026

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

@mcharriere
Copy link
Copy Markdown
Contributor Author

/run cluster-test-suites TARGET_SUITES=./providers/capa/standard

1 similar comment
@mcharriere
Copy link
Copy Markdown
Contributor Author

/run cluster-test-suites TARGET_SUITES=./providers/capa/standard

@tinkerers-ci
Copy link
Copy Markdown

tinkerers-ci bot commented Apr 14, 2026

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

@mcharriere
Copy link
Copy Markdown
Contributor Author

/run cluster-test-suites TARGET_SUITES=./providers/capa/standard

@mcharriere
Copy link
Copy Markdown
Contributor Author

/run cluster-test-suites

@mcharriere mcharriere marked this pull request as ready for review April 20, 2026 11:42
@mcharriere mcharriere requested a review from a team April 20, 2026 11:42
Copy link
Copy Markdown
Contributor

@QuantumEnigmaa QuantumEnigmaa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Copy Markdown
Member

@ubergesundheit ubergesundheit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@tinkerers-ci
Copy link
Copy Markdown

tinkerers-ci bot commented Apr 20, 2026

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/china,./providers/capa/private,./providers/capv/on-capz,./providers/capz/private

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>
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>
@mcharriere
Copy link
Copy Markdown
Contributor Author

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

@mcharriere
Copy link
Copy Markdown
Contributor Author

/run cluster-test-suites

@tinkerers-ci
Copy link
Copy Markdown

tinkerers-ci bot commented Apr 20, 2026

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/china,./providers/capa/cilium-eni-mode,./providers/capa/private,./providers/capa/standard,./providers/capv/on-capz,./providers/eks/standard

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants