Resolve JVB crash loop — wrong MUC JID + port 8080 conflict

Порезанный

30 марта 2026 г. в 17:21 UTC

Автор

Kamo

Обещать

6a27c82

Two issues causing JVB to crash in a loop for 43+ hours: 1. JVB_BREWERY_MUC was **************** (full JID) but JVB appends XMPP_INTERNAL_MUC_DOMAIN automatically, creating **************** which has @ in the domain — XmppStringprepException crash. Fix: changed to just "jvbbrewery" (room name only) 2. JVB health REST API binds port 8080, which conflicts with CockroachDB's admin UI on the same hostNetwork. Jetty fails to bind → crash. Fix: changed to port 8888 via JVB_OHTTP_SERVER_PORT, updated probes Both k1m1 and k2m1 statefulsets updated.