Add v1 api to e2e tests#4334
Merged
dsessler7 merged 2 commits intoCrunchyData:mainfrom Nov 14, 2025
Merged
Conversation
ValClarkson
approved these changes
Nov 13, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Checklist:
Type of Changes:
What is the current behavior (link to any open issues here)?
Currently, the kuttl and chainsaw tests are hardcoded to use the v1beta1 postgrescluster API.
What is the new behavior (if this is a feature change)?
Now, there are variables that can be used to set the postgrescluster API used by the kuttl and chainsaw tests. For kuttl, an environment variable,
KUTTL_PGCLUSTER_API_VERSION, is set in thegenerate-kuttlmake target. For chainsaw,versions.postgresclusteris set in the values.yaml file. The default for both is nowv1.There is also a commit to refactor an API CEL validation test.
Other Information: