- Shipped
- 13 Agosti 2026, 02:10 UTC
- Author
- Kamo
- Commit
- 34ca31c
CockroachDB v24.2.4 was pinned to the last release under the old free BSL terms and was replaced by YugabyteDB on 2026-08-09. Nothing has connected to it since; parity re-verified before removal (kamo 728/728 tables, kamouniverse 111/111, OCR rows identical). Removed: cockroachdb/ (StatefulSet, Services, init Job, cert template and the five committed TLS files), **************** the two CI steps that built *** and applied those manifests, and migration/crdb2yb/ whose one job — moving the data — is done. Kept deliberately, because renaming them means touching every consumer for no gain: the Secrets *** and universe-cockroachdb-url (both already hold Yugabyte values) and the MinIO bucket cockroach-backups (holds the live universe dumps). Two latent bugs surfaced while sweeping the references: - The CockroachBackupMissing alert matched **************** but the CronJob is named kamouniverse-backup. max() over an empty series set yields no result, so the rule could never fire — a backup gap would have gone unnoticed. Renamed to UniverseBackupMissing with a matcher that hits. - **************** still listed 26257 while the live CiliumNetworkPolicy had been given 5433 out of band. Harmless today (this file is not a CI apply target) but the committed copy described a policy that would have cut SecurityService off from its database. deploy-services.yml now verifies the yb-master/yb-tserver StatefulSets in place of cockroachdb. CLUSTER_SYNC_STATUS.md is deleted: a 2026-02-02 point-in-time report about a three-node CRDB cluster and k0m1, both retired.