feat(edge): manage demo edges with applicationset
This commit is contained in:
1 parent
a67c251486
commit
3cad414953
4 files changed
+52
-31
No files matched your search
@@ -17,11 +17,13 @@ Demo environment:
|
||||
2. Apply or create `bootstrap/mixingx-demo-root.yaml`.
|
||||
3. Argo CD will create/sync the applications under `applications/`.
|
||||
|
||||
Agent fleet:
|
||||
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.
|
||||
- Add or remove agent instances by editing `spec.generators[0].list.elements` in `applications/agents.yaml`.
|
||||
- `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:
|
||||
@@ -34,4 +36,8 @@ kubectl label node node1 mixingx.io/edge-node=shanghai
|
||||
- id: shanghai
|
||||
description: Shanghai Agent
|
||||
nodeLabel: shanghai
|
||||
|
||||
- id: beijing
|
||||
description: Beijing Edge
|
||||
nodeLabel: beijing
|
||||
```
|
||||
Reference in new issue
Block a user