ximenchuifeng 56207aa5e1 feat(ci): promote.sh supports PLAN-based per-service partial delivery
Replace the all-or-nothing baseline with a per-service plan (PLAN JSON):
keep/reuse/deliver/ci-now per service pair (gateway/sso/ultra/audit/
agent/edge). Compat params SERVICES/IMAGES map to deliver entries; all
params empty = full delivery of demo tags, pin output byte-identical to
the old script. Version/chart tag only allocated when needed; existing
chart tag is reused idempotently instead of failing. retag records image
digests; pin writes prepended release-notes.yaml entries (from/to,
sourceTag, digest, dbChange) and only touches files of non-keep
services. CHART_ONLY skips image work. PROMOTE_DRY_RUN echoes docker
and git push for local rehearsal.

Design: hub docs/adr/0074 (partial delivery alongside ADR-0067).
2026-08-27 14:37:09 +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%