CouchDB and RabbitMQ on k3m1

FeatureKlusterServices
Ya
27 Agosti 2026, 07:02 UTC
Mwandishi
Kamo
Ahadi ya
4ee0594

CouchDB q=8 / n=1, verified live. q is fixed at database creation and KamoPBX creates a database per account plus monthly MODBs, so q is sized now for the eventual 3-node cluster; n can be raised later by editing shard maps, q cannot. Auto-compaction enabled — upstream ships it off and KamoPBX's write pattern fragments badly. Three deployment bugs found and fixed live: - Mounting the ConfigMap over /opt/couchdb/etc/local.d makes it read-only and the entrypoint dies writing docker.ini. Uses subPath for the single file. - A fresh Longhorn volume is root-owned; couchdb runs as uid 5984 and exited 1 with no log output at all. Added fsGroup plus a chown initContainer. - rabbitmq-diagnostics needs more than the default 1s probe timeout; the server was healthy (9s startup) but the probe failed it. RabbitMQ runs as kamopbx, not the shipped guest:guest with loopback_users off.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei