Repository navigation
[release-1.10] chore(ci): replace Crunchy Postgres operator with RHEL PostgreSQL StatefulSet - #5835
Conversation
|
/test e2e-ocp-operator-nightly |
|
/test e2e-ocp-v5-0-helm-nightly |
PR Summary by QodoReplace Crunchy PostgreSQL with a StatefulSet in release-1.10 CI
AI Description
Diagram
High-Level Assessment
Files changed (16)
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## release-1.10 #5835 +/- ##
=================================================
+ Coverage 41.03% 69.69% +28.65%
=================================================
Files 121 111 -10
Lines 2220 4715 +2495
Branches 563 535 -28
=================================================
+ Hits 911 3286 +2375
- Misses 1303 1428 +125
+ Partials 6 1 -5
Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
…tefulSet The Crunchy Postgres operator is not available in the OCP 5.0 certified-operators catalog (crunchy-postgres-operator is published for OCP 4.15-4.22 only), so every OCP job fails before the tests start. On top of that, Crunchy announced that the Developer Program images our PostgresCluster pulls will stop receiving updates on 2026-12-31. Deploy the external PostgreSQL used by showcase-rbac as a plain StatefulSet running registry.redhat.io/rhel9/postgresql-16 instead: - TLS server certificate generated by the CI script (CA + cert with SANs for the Service DNS names), served from the same postgress-external-db-cluster-cert secret the RBAC values mount. - The start hook restricts network connections to TLS and creates the rhdh SUPERUSER from postgress-external-db-pguser-rhdh. - The registry.redhat.io pull secret is created from the existing REGISTRY_REDHAT_IO_SERVICE_ACCOUNT_DOCKERCONFIGJSON CI secret. The Crunchy operator install and the PostgresCluster CRD waits are removed. Also rename the external DB TLS spec and update the CI docs accordingly. Adaptations for release-1.10: - Use PostgreSQL 16: 1.10 supports PostgreSQL 14-17 and Red Hat does not ship a rhel9/postgresql-17 image. Use ssl_ecdh_curve instead of ssl_groups, which only exists in PostgreSQL 18 and would prevent the server from starting. - Keep the OpenShift Pipelines install in cluster_setup_ocp_helm and cluster_setup_ocp_operator, and their call sites, since the branch installs Pipelines on OCP. Only the Crunchy install is dropped, so operator::install_subscription and operator::install_pipelines stay in lib/operators.sh while the Crunchy helper and the OLM status helper it used are removed. - Drop the k8s_wait::deployment wait for postgress-external-db, which no longer exists as a Deployment. - The operator job runtime tests also use the external PostgreSQL, so keep configuring it there and keep the second call idempotent through the reused certificates and credentials. - Do not add changes to files that do not exist on this branch (ocp-fips-helm.sh, runtime-deploy.ts, layer-migration-matrix.md) or to the cloud value files, which have no Crunchy reference here. - The pr-triage content lives in .rulesync/commands here, so the edits are applied to that source and the generated copies are regenerated. Jira: https://redhat.atlassian.net/browse/RHDHBUGS-4113 Assisted-by: OpenCode (cherry picked from commit 6e6cd04)
410f750 to
35550a9
Compare
|
|
/lgtm |
|
@zdrapela: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/retest |
|
/test e2e-ocp-helm |
ce171b3
into
redhat-developer:release-1.10



Manual backport of #5820 to release-1.10.
Replaces the Crunchy Postgres operator with a plain StatefulSet for the external
PostgreSQL used by showcase-rbac and showcase-runtime. The Crunchy operator is not
published for OCP 5.0, so every OCP job fails before the tests start.
Adaptations for release-1.10:
registry.redhat.io/rhel9/postgresql-16): 1.10 supportsPostgreSQL 14-17 and Red Hat does not ship a
rhel9/postgresql-17image.ssl_ecdh_curvereplacesssl_groups, which only exists in PostgreSQL 18.cluster_setup_ocp_helm,cluster_setup_ocp_operatorand their call sites are kept and only the Crunchyinstall is removed.
postgress-external-dbDeployment, which no longerexists, and kept the external DB setup for the operator runtime tests.
ocp-fips-helm.sh,runtime-deploy.ts,layer-migration-matrix.md) or to the cloud value files..rulesync/commandshere, so the edits wereapplied there and the generated copies regenerated.
Validation
ci/prow/e2e-ocp-helme2e-ocp-operator-nightlye2e-ocp-v5-0-helm-nightlyLocal: shellcheck (
-x -S warning),bash -n,prettier --check,eslint,tsc,playwright test --list,rulesync generate --check.The PostgreSQL 16 StatefulSet works. The operator nightly deployed it and
ran the schema-mode tests against it:
The
v5-0-helm-nightlyfailure is not caused by this change.showcaseruns onits own in-cluster database there, and the smoke test failed all 11 attempts in
both
showcaseandshowcase-rbac: the home page renders, butwaitForSelector("nav a")never matches and the browser reportsFailed to fetch.Everything else in those projects was then skipped, and the runtime suite hit the
2h pod timeout. This needs a separate look at 1.10 on OCP 5.0.
Jira: https://redhat.atlassian.net/browse/RHDHBUGS-4113