Skip to content

fix: update CRD path in controller tests after Helm migration#13

Merged
STRRL merged 2 commits intomasterfrom
fix/controller-test-crd-path
Feb 23, 2026
Merged

fix: update CRD path in controller tests after Helm migration#13
STRRL merged 2 commits intomasterfrom
fix/controller-test-crd-path

Conversation

@STRRL
Copy link
Owner

@STRRL STRRL commented Feb 23, 2026

Summary

  • Update envtest CRD path from config/crd/bases to helm/supabase-operator/crds in internal/controller/suite_test.go
  • The old kustomize path was removed during the Helm migration (ceb8595), breaking controller tests in CI

Closes #12

Test plan

  • make test passes locally with all controller tests succeeding

Rename S3_ENDPOINT to GLOBAL_S3_ENDPOINT and add required env vars
(GLOBAL_S3_FORCE_PATH_STYLE, TENANT_ID, REGION, POSTGREST_URL) for
compatibility with newer storage-api. Bump default resource limits and
update image to v1.32.0. Adjust e2e test Chrome flags and timeout.
The envtest CRD path still referenced the old kustomize location
(config/crd/bases) which was removed in the Helm migration. Update
to the new path (helm/supabase-operator/crds).

Closes #12
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: da632a0c3e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

},
{
Name: "S3_ENDPOINT",
Name: "GLOBAL_S3_ENDPOINT",

Choose a reason for hiding this comment

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

P1 Badge Preserve S3_ENDPOINT until storage CRD default is upgraded

This change removes the legacy S3_ENDPOINT env var and only sets GLOBAL_S3_ENDPOINT, but the shipped CRD/API defaults for spec.storageAPI.image are still supabase/storage-api:v1.25.7 (helm/supabase-operator/crds/supabase.strrl.dev_supabaseprojects.yaml:1473, api/v1alpha1/supabaseproject_types.go:180). In the common case where users set spec.storageAPI fields but omit image, admission defaulting can keep v1.25.7, and that version expects the legacy endpoint variable; the pod then starts with incompatible env configuration and storage cannot connect to S3.

Useful? React with 👍 / 👎.

@STRRL STRRL merged commit cb04d3d into master Feb 23, 2026
5 checks passed
@STRRL STRRL deleted the fix/controller-test-crd-path branch February 23, 2026 06:43
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.

fix: controller tests fail due to missing CRD path after Helm migration

1 participant