Read 2026-11-03
crunchydata/postgres-operator: technical due diligence, read from its repository
What Borehole read in crunchydata/postgres-operator's code and history at 547c38f: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | adequate |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | strong |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
adequateinternal/controller/postgrescluster/pgbackrest.go is 3,370 lines, 24× this codebase's median file
adequateThe median source file here is 137 lines. 2 files exceed 1,370 lines, the largest being 3,370. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.
internal/controller/postgrescluster/pgbackrest.go:1 — 3,370 lines (24× median) |
internal/controller/postgrescluster/instance.go:1 — 1,567 lines (11× median) |
9 base images float: no version, or `latest`
adequate9 of 14 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
components/image-collector/Dockerfile:11 — base image without a version |
components/image-collector/Dockerfile:32 — base image without a version |
components/image-exporter/Dockerfile:5 — base image without a version |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
strong5 of 5 Kubernetes workloads declare no resource limits
adequate5 workload manifests set no CPU or memory limits. One pod that leaks memory or spins can starve everything else on its node, and the scheduler cannot plan capacity for what it cannot see.
config/dev/manager-dev.yaml — workload with no limits |
config/manager/manager.yaml — workload with no limits |
config/monitoring/alertmanager/deployment.yaml — workload with no limits |
Observability & Operations
adequateReadiness and liveness probes are identical in 1 of 4 workloads
adequateBoth probes call the same endpoint. When a dependency slows down, the liveness probe fails with the readiness probe, so the platform restarts pods that only needed taking out of rotation, and a partial outage becomes a full one. Liveness should ask whether the process is alive; readiness whether it can serve.
config/monitoring/grafana/deployment.yaml — same probe endpoint twice |
1 of 5 deployments run a single replica
adequate1 deployments set `replicas: 1`, and nothing (an autoscaler, a disruption budget) adds more. Every deploy and every node drain is downtime, and the availability the buyer inherits has a ceiling.
config/manager/manager.yaml — replicas: 1 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on crunchydata/postgres-operator: every dimension, the questions for the room, and the audit log.
Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.