e26d1934d617eb19b9e6027037a0a42a7525e78a
添加了完整的 basic-test 环境配置文件,包括: - 创建了 9 个 ArgoCD Application 和 ApplicationSet 配置文件: - agents.yaml: Agent 单元应用集配置 - audit.yaml: 审计服务应用配置 - edges.yaml: Edge 单元应用集配置 - gateway.yaml: 网关服务应用配置 - infra.yaml: 基础设施应用配置 - longhorn.yaml: Longhorn 存储应用配置 - sso.yaml: SSO 单点登录应用配置 - ultra.yaml: Ultra 看板应用配置 - bootstrap/mixingx-basic-test-root.yaml: 基础测试根应用配置 - 添加了 9 个环境变量值文件: - agent-common-values.yaml: Agent 通用配置 - agents.yaml: Agent 实例定义 - audit-values.yaml: 审计服务配置 - edge-common-values.yaml: Edge 通用配置 - edges.yaml: Edge 实例定义 - gateway-values.yaml: 网关配置 - image-version.yaml: 镜像版本配置 - infra-values.yaml: 基础设施配置 - single-node-values.yaml: 单节点部署配置 - sso-values.yaml: SSO 服务配置 - ultra-values.yaml: Ultra 服务配置 这些配置支持通过 ApplicationSet 动态生成多个 Agent 和 Edge 实例, 并包含了完整的单节点测试环境部署所需的所有组件。
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%