ximenchuifeng 21617e385b release: mxlexus 交付 v1.0.5(chart-v1.0.5)
服务清单:
- mqttx: pin-acr latest → latest(source: latest)
- nanomq: pin-acr 0.25.2-2 / 0.25.2-2 → 0.25.2-2(source: 0.25.2-2)
- postgres: pin-acr 17 / 17 / 17 / 17 → 17(source: 17)
- rabbitmq: pin-acr 4.3-management → 4.3-management(source: 4.3-management)
- redis: pin-acr 8.6 → 8.6(source: 8.6)
其余服务保持现状(keep): gateway, sso, ultra, audit, agent, edge, wifi

release-notes: 阿水淀粉

operator: admin
2026-09-08 07:03:02 +00: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%