Cluster · Nodes · Namespaces · Workloads · Storage
The Kubernetes control panel — cordon and drain nodes, namespaces and workloads, and storage
Required permission: Global admin
Geo-MLOps runs training Jobs, serving and image builds on a single Kubernetes cluster. The cluster is a resource shared by all tenants, so this control panel is open only to global administrators (every server route requires a global administrator). If the cluster is not connected, each screen shows "Kubernetes not connected (Kubernetes 미연결)" and the reason.
Cluster overview
Shows the number of active nodes, the number of active Pods, the Ready ratio, and a summary per node pool (a group of nodes bundled by node label). It is a screen to skim once a day.
Nodes — cordon and drain
The node list shows pool, state, CPU, memory and GPU, Pod count and version. Press a row to see its conditions, taints and the pods on that node in the side panel, so you can check what will be affected before you act.
| Action | What it does | Undo |
|---|---|---|
| Cordon | Stops new pods from being scheduled on the node. Pods already running stay | Uncordon (Uncordon) |
| Drain | Evicts every pod on the node. Any training or serving is stopped immediately and rescheduled on other nodes | Cannot be undone |
- Press Cordon (Cordon) on the node to be serviced so that no new work comes in.
- Wait for running work to finish, or press Drain (Drain) if you cannot wait. It runs only after you type the node name exactly.
Drain confirmation — requires typing the node name (not executed here) - When maintenance is done, undo it with Uncordon (Uncordon).
Namespaces
Every namespace in the cluster appears as a card; press a card to go to the workloads screen of that namespace. Each tenant has one tenant-{lower-case code} namespace (for example tenant-demo). System namespaces, such as the one for shared images, appear as well.
In the screen above, tenant namespaces not used for the screenshots are masked.
Workloads
Choose a namespace at the top right and browse by kind tab (Deployment, StatefulSet, DaemonSet, Job, CronJob, Pod).
| Button | What it does |
|---|---|
| Restart (Restart) | Restarts the rollout (brings up new pods one after another). Asks for confirmation |
| Scale (Scale) | Changes the replica count |
| Delete (Delete) (Pod tab) | Deletes one pod. If it has a controller, a new one comes up |
Storage
Shows StorageClass cards, a PersistentVolume table (whole cluster) and a PersistentVolumeClaim table (pick a namespace). It is read-only. PVCs also show actual usage, so you can find volumes that say "Bound 100Gi" but are full and make training fail. Volumes without statistics show —, not 0.