You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
***Cluster** level descritptions, require a file for each cluster registered in Karmada. It contains the clusterID and a list of node hostnames, that MLSysOps is allowed to manage.
53
53
***Node** level descriptions, contain the detailed information about the node resources. Example [here](descriptions/nodes/node-1.yaml).
54
54
55
-
#### Step 2: Automated Deployment
55
+
Before deploying, prepare system descriptions as Kubernetes CRDs:
56
56
57
-
MLSysOps CLI tool can be used to automatically deploy all the necessary components.
58
-
It needs the kubeconfigs of Karmada host cluster and Karmada API.
57
+
- Stored in the `descriptions/` directory
59
58
60
-
-`export KARMADA_HOST_KUBECONFIG=<path to karmada host kubeconfig>`
61
-
-`export KARMADA_API_KUBECONFIG=<path to karmada api kubeconfig>`
62
-
-`export KARMADA_HOST_IP=<karmada host ip>`
59
+
### 📁 File structure:
63
60
64
-
And then execute the CLI command inside `deployments` directory, with `descriptions` directory files prepared:
65
-
-`cd deployments`
66
-
-`python3 deploy.py`
61
+
```
62
+
descriptions/
63
+
├── continuum/
64
+
│ └── <continuum-hostname>.yaml
65
+
├── clusters/
66
+
│ └── <cluster-hostname>.yaml
67
+
└── nodes/
68
+
└── <node-hostname>.yaml
69
+
```
67
70
71
+
Descriptions define IDs, managed components, and resource details. All files are required before installation.
68
72
69
-
Wait for the MLSysOps framework to be deployed, and you can check if the agents are running with:
0 commit comments