56207aa5e1c04936bb088caa1196718aa93ba2d6
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).
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:
- Register both repositories in Argo CD:
https://gitee.com/mixing-tech/mixingx.deploy.githttps://gitee.com/mixing-tech/mixingx.hub.chart.git
- Apply or create
bootstrap/mixingx-demo-root.yaml. - 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 inmixingx.hub. - Its manifests are kept inert under
applications/dev/disabled/andbootstrap/disabled/; values underenvironments/dev/are kept for reference. - See
applications/dev/README.mdfor the rationale and re-enable steps.
Agent and edge fleets:
applications/agents.yamlis an Argo CD ApplicationSet.applications/edges.yamlis an Argo CD ApplicationSet.environments/demo/agent-common-values.yamlcontains shared Helm values for all agents.environments/demo/edge-common-values.yamlcontains shared Helm values for all edges.- Add or remove agent or edge instances by editing
spec.generators[0].list.elementsin the matching ApplicationSet. - Prefer
nodeLabelovernodeName; 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
Languages
Shell
100%