- Shipped
- August 9, 2026 at 10:35 PM UTC
- Author
- Kamo
- Commit
- cdf09c3
Both engines now run side by side on k1m1; CockroachDB is untouched and remains the rollback path. Three things that were not obvious: - The Helm chart version is not the Docker tag. Chart 2026.1.0 maps to app version 2026.1.0.0-b118, so `image: yugabytedb/yugabyte:2026.1.0` is ImagePullBackOff. Pinned to 2026.1.0.1-b1, newest patch of stable 2026.1. - hostNetwork puts the pods on k1m1's real interfaces, where two Yugabyte defaults are already taken: 9000 by MinIO and 9100 by node_exporter. The tserver webserver moves to 9010 and its RPC to 9110. Both host services verified unaffected afterwards. - TLS is not optional. All 31 consumer connection strings carry sslmode=require, so YSQL without encryption would refuse every client at cutover. Certs are created out of band, with the cockroachdb-public alias name in the SAN list because consumers keep using it through cutover. Deliberately not wired into CI: adding a deploy step edits .forgejo/, which triggers a full reconcile that reverts live drift.