Skip to content

Install Envoy Gateway CRDs before testing service-gateway in CI - #1393

Merged
ArnobKumarSaha merged 1 commit into
masterfrom
arnob-gw-crds-ci
Nov 4, 2026
Merged

ArnobKumarSaha merged 1 commit into
masterfrom
arnob-gw-crds-ci

Conversation

@ArnobKumarSaha

Copy link
Copy Markdown
Member

Since #1388, service-gateway always renders EnvoyProxy. Its CRD is installed by the voyager-gateway crd-manager pre-install hook, but helm maps every manifest kind before running hooks, so ct install fails on the fresh test cluster:

Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: resource mapping not found ... no matches for kind "EnvoyProxy" in version "gateway.envoyproxy.io/v1alpha1"

Failing run: https://github.com/appscode-cloud/installer/actions/runs/41639561493/job/125933044583

Changes:

  • hack/scripts/install-gateway-crds.sh: installs the vendored crd-manager subchart (from charts/service-gateway/charts/voyager-gateway-*.tgz) as a throwaway release so its hook Job creates the CRDs, then uninstalls the release.
  • hack/scripts/ct.sh: for service-gateway, delete CRDs, install the gateway CRDs, and run make ct with CT_CLEANUP=false (otherwise make ct wipes the CRDs first).
  • hack/scripts/test-service-gateway.sh: install the gateway CRDs first, since that CI step deletes all CRDs beforehand.

CI-only fix; a plain helm install of service-gateway on a cluster without the Envoy Gateway CRDs still fails.

Signed-off-by: Arnob Kumar Saha <arnob@appscode.com>
@ArnobKumarSaha
ArnobKumarSaha merged commit 09b6266 into master Nov 4, 2026
8 checks passed
@ArnobKumarSaha
ArnobKumarSaha deleted the arnob-gw-crds-ci branch November 4, 2026 09:49
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.

1 participant