ximenchuifeng a1a1a617ff feat(release): 交付晋级流水线 release-promote(本仓库第一条流水线)
- .drone.yml: 四步(prepare/retag/chart/pin),trigger 仅 custom,push 事件零触发
- ci/promote.sh: 读 demo 交付基线→retag 推 ACR→chart bump+tag→release 分支钉版
- ci/auto-bump.sh: 未传版本号时自动递增 patch(查 chart tag)
- 凭证: ACR 推送走 secrets(已配);git push 走 netrc;禁止凭证走参数(ADR-0066/0067)
2026-08-22 13:08:42 +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/.

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%