fb83035a1594887323ae4a906b50ec2315abfc1b
交付基线(develop tag 组合,源自 demo image-version):
gateway develop-v.1.0.1-202608050744-6
sso develop-v.1.0.1-202608200414-37
sso-web develop-v.1.0.1-202608200414-37
ultra develop-v.1.0.1-202608200309-30
ultra-web develop-v.1.0.1-202608200309-30
audit develop-v.1.0.1-202608200523-8
edge develop-v.1.0.1-202608111317-42
edge-web develop-v.1.0.1-202608111317-42
agent develop-v.1.0.1-202608200909-72
agent-web develop-v.1.0.1-202608200909-72
chart: chart-v1.0.1
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/.
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%