Files
mixingx.hub.chart/README.md
T

59 lines
2.8 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# MixingX.Hub.Chart
本仓库以 git submodule 形式挂载在 [mixingx.hub](https://gitee.com/mixing-tech/mixingx.hub) 的 `mixingx-chart/` 路径下。CI(Drone)和 ArgoCD 都通过 `release-charts/` 子目录访问,改路径名会破坏部署链路。
## 拆分 Release Charts(唯一部署入口)
所有部署(CI lint/template、ArgoCD Application)都使用 `release-charts/` 下的拆分 unit chart,不再有单体主 chart:
| Chart | 职责 |
|---|---|
| `release-charts/mixingx-infra` | 共享基础设施(redis/mongo/rabbitmq/postgres) |
| `release-charts/mixingx-platform` | 中央平台服务(sso/ultra/audit/gateway) |
| `release-charts/mixingx-edge-unit` | 单个 Edge 单元(后端+前端+独立 DB+NanoMQ broker) |
| `release-charts/mixingx-agent-unit` | 单个 Agent 单元(后端+前端+独立 DB) |
| `release-charts/mixingx-gateway` | Gateway(带 MQTT broker 发现 RBAC) |
| `release-charts/mixingx-sso` | SSO(独立发布) |
| `release-charts/mixingx-ultra` | Ultra(独立发布) |
| `release-charts/mixingx-audit` | Audit(独立发布) |
| `release-charts/mixingx-protocol-server-unit` | 协议模拟器单元 |
每个 chart 独立 `helm release`,平台升级不会误删客户自加的 edge/agent 单元。
## 使用
### CI(Drone)lint + template
CI 只对 `release-charts/` 做 lint/template(见 hub `.drone.yml`):
```bash
helm lint release-charts/mixingx-edge-unit
helm template ci-edge release-charts/mixingx-edge-unit
```
### ArgoCD 部署
`mixingx-deploy` 的 ApplicationSet 按 unit chart 逐个发布,每个 edge/agent 一个独立 Helm release。详见 `mixingx-deploy/`。
## PostgreSQL on K3s
PostgreSQL StatefulSets use the Debian image's UID/GID 999 and run the image
entrypoint directly. This skips gosu while preserving database initialization
and startup on the existing data volume. The readiness probe uses
`pg_isready` over TCP so the container is Ready only after PostgreSQL accepts
connections, including after recovery.
Only the PostgreSQL container uses `privileged: true` as a temporary workaround
for checkpoint signal failures observed on affected Ubuntu 26.04 / K3s nodes.
The namespace's admission policy must permit privileged containers. The
[containerd signal-denial report](https://github.com/containerd/containerd/issues/14485)
describes the same checkpoint error with AppArmor. Check the host kernel log
for an AppArmor signal denial and validate initialization and recovery with the
corrected runtime or profile before removing privileged mode.
## 关联文档
- hub [AGENTS.md](https://gitee.com/mixing-tech/mixingx.hub) — 全项目指南
- `mixingx-deploy/` — ArgoCD Application + 环境 values
- `docs/superpowers/specs/2026-07-01-node-tier-affinity-design.md` — 三层调度设计