chenhuan f4167d4a5b demo: enable auto-sync on all demo apps and ApplicationSets
Add syncPolicy.automated (prune=false, selfHeal=true) to all demo
Application definitions and ApplicationSet templates under
applications/demo/ so manifest changes (image/chart version pins from
the release pipeline) are applied by ArgoCD automatically.

- 11 Application manifests + disabled/platform-legacy now auto-sync
- 3 ApplicationSet templates (agents/edges/protocol-servers) now
  propagate auto-sync to generated apps
- codeserver and mixingx-demo-root already had it, unchanged
- bootstrap/mixingx-demo-root.yaml unchanged (already automated)
2026-11-03 11:33:59 +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%