Kubernetes
Learn how to view and manage Kubernetes resources in your cluster using the Kubo UI.
Related: Deploy Applications / Backups
Viewing Resources
Open the "Kubernetes" tab on the cluster details page to browse resources by type:
- Workloads: Pod / Deployment / ReplicaSet / StatefulSet / Job / CronJob
- Network: Service / Ingress
- Config: ConfigMap / Secret
- Storage: PersistentVolume (PV) / PersistentVolumeClaim (PVC) / StorageClass
- Cluster: Node / Namespace
- Other: Helm releases / RBAC / Debug & Events
Every list shows common columns (Name / Namespace / Kind / Created) plus type-specific columns. Click a row to open the detail panel for information that isn't shown in the list.
Pods
Pods are the basic execution units for your applications. The list shows Node / CPU / Memory / Status; the detail panel adds containers, restart count, events, and more.
Services
Services manage network access to your applications within and outside the cluster. The list shows the common columns; Type (ClusterIP / NodePort / LoadBalancer) and Ports are available in the detail panel (click a row).
Deployments
Deployments manage the deployment state of your applications. The list shows Replicas / Ready / Available; the container image and pod template are in the detail panel. (ReplicaSets and StatefulSets use the same column layout.)
Ingresses
Ingresses route external HTTP traffic to your services. The list shows the common columns; Host (domain) and Path are available in the detail panel.
Local Access
You can also download the kubeconfig file and access the cluster via kubectl from your local environment.
Downloading kubeconfig
- Open the cluster details page
- From the menu (⋮) at the top right, choose "Download Kubeconfig"
- The file is downloaded
Configuring kubectl
export KUBECONFIG=/path/to/downloaded/kubeconfig.yaml
# Check nodes
kubectl get nodes
# Check pods across all namespaces
kubectl get pods -A
# Check services
kubectl get services -A
# Check deployments
kubectl get deployments -A
Troubleshooting
Pod Won't Start
# Check Pod details
kubectl describe pod <pod-name> -n <namespace>
# Check Pod logs
kubectl logs <pod-name> -n <namespace>
Common causes:
- Container image not found (ImagePullBackOff)
- Insufficient resources (Insufficient CPU / Memory)
- Configuration errors (CrashLoopBackOff)
Cannot Access a Service
# Check Service details
kubectl describe service <service-name> -n <namespace>
# Check Endpoints
kubectl get endpoints <service-name> -n <namespace>