Files
mixingx.hub.chart/release-charts
ximenchuifeng f972154abf fix(edge-unit): backend Deployment 改用 Recreate 策略
Edge backend 启动时通过 EdgeOwnerLease 对 PVC data root
(/var/lib/mixingx-edge/owner.lock)取排他文件锁,保证同一 data root
同时只有一个写者。默认 RollingUpdate 会先起新 Pod 再杀旧 Pod,新旧
共享同一 PVC → 新 Pod 抢 owner.lock 失败 → Fatal → CrashLoopBackOff
→ 滚动永久卡死、ArgoCD Application 持续 Degraded。

改用 Recreate:先杀旧 Pod(释放锁)再起新 Pod(拿锁成功),与单实例
有状态服务的语义匹配。PVC 全程不受影响,数据零丢失。
2026-08-06 08:59:44 +08:00
..

MixingX Split Charts

This directory contains the release-oriented charts for Phase 1 ownership split:

  • mixingx-infra: shared Redis, MongoDB, RabbitMQ.
  • mixingx-gateway: gateway service, RBAC, and root ingress.
  • mixingx-sso: SSO backend, web frontend, and dedicated PostgreSQL.
  • mixingx-ultra: Ultra backend, web frontend, and dedicated PostgreSQL.
  • mixingx-audit: Audit service (uses shared Mongo/RabbitMQ).
  • mixingx-edge-unit: one edge site release.
  • mixingx-agent-unit: one agent site release.
  • mixingx-protocol-server-unit: one protocol mock server instance.
  • mixingx-platform: legacy central-services chart, kept for compatibility during migration.

The chart at the repository root is kept as a legacy all-in-one chart during migration.