ximenchuifeng 6450d3084c feat(ci): PLAN 动态映射——条目自带 repos/keys/appFile/valuesFiles 即信任(格式校验),三张字典降级为缺省
- ADR-0075 加服务不改程序:门户登记映射(DB)随 PLAN 条目透传,promote 端信任执行
- valuesFiles 钉版新路径(独立 chart 服务如 wifi):替换客户 values 的 image.tag,
  兼容整行 repo:tag / repository+tag 拆分 / image 块三形态
- keys 空 → 不动 image-version;appFile 空 → 不随统一 chart(独立 chart 自然编码)
- deliver 缺省 harborTag:有 keys 查 image-version,无 keys 查 demo 的 values 文件
- ALL → DEFAULT_SERVICES(缺省全量 deliver 名单);DB_CHANGE 按计划内服务校验
- 兼容:六服务不带映射回退字典;未知服务非 keep 拒绝、keep 放行(留痕)
- 演练:PROMOTE_DRY_RUN 双路径(wifi pin-acr 钉直推 tag / deliver retag 新版本)+
  缺省全量回归,均在 /tmp 沙盒 GIT_CONFIG_GLOBAL 隔离下通过
2026-09-08 14:52:54 +08:00

MixingX Deploy

This repository is the GitOps environment state for MixingX deployments.

Responsibilities:

  • applications/: Argo CD Application manifests.
  • environments/: environment-specific Helm values.
  • Helm chart templates live in mixingx.hub.chart.git.
  • Application source code and CI live in mixingx.hub.git.

Demo environment:

  1. Register both repositories in Argo CD:
    • https://gitee.com/mixing-tech/mixingx.deploy.git
    • https://gitee.com/mixing-tech/mixingx.hub.chart.git
  2. Apply or create bootstrap/mixingx-demo-root.yaml.
  3. Argo CD will create/sync the applications under applications/.

Dev environment (retired):

  • The dev environment (namespace mixingx-dev, dev.mixingx.local) is retired; local development is covered by Aspire in mixingx.hub.
  • Its manifests are kept inert under applications/dev/disabled/ and bootstrap/disabled/; values under environments/dev/ are kept for reference.
  • See applications/dev/README.md for the rationale and re-enable steps.

Agent and edge fleets:

  • applications/agents.yaml is an Argo CD ApplicationSet.
  • applications/edges.yaml is an Argo CD ApplicationSet.
  • environments/demo/agent-common-values.yaml contains shared Helm values for all agents.
  • environments/demo/edge-common-values.yaml contains shared Helm values for all edges.
  • Add or remove agent or edge instances by editing spec.generators[0].list.elements in the matching ApplicationSet.
  • Prefer nodeLabel over nodeName; label the target node so Kubernetes scheduler can still bind local-path PVCs.

Example:

kubectl label node node1 mixingx.io/edge-node=shanghai
- id: shanghai
  description: Shanghai Agent
  nodeLabel: shanghai

- id: beijing
  description: Beijing Edge
  nodeLabel: beijing
S
Description
auto-mirrored from internal gitea
Readme
968 KiB
0 Stars 1 Watchers 0 Forks
Languages
Shell 100%