Overview
Native Kubernetes support in Dockerman — workloads, networking, config, storage, RBAC, CRDs, Helm, and debug.
Dockerman's Phase 1 Kubernetes support is a lightweight, GUI-first way to run and inspect a real Kubernetes cluster without switching tools or learning a new dashboard.
Why Kubernetes in Dockerman
Use Dockerman when you want Kubernetes in the same app you already use for Docker. Keep the interface local and fast, bring k3d along for one-click cluster setup, and stay inside a native Rust and Tauri desktop app instead of jumping to another dashboard. It is lighter than Docker Desktop's built-in Kubernetes path and fits local development, small clusters, and CI sanity checks.
What's included
Cluster
Start local k3d clusters or import existing kubeconfigs.
Workloads
Browse Pods, Deployments, StatefulSets, DaemonSets, Jobs, CronJobs, and ReplicaSets.
Networking
Inspect Services, Ingresses, Endpoints, and NetworkPolicies.
Config & Storage
Work with ConfigMaps, Secrets, PVCs, and StorageClasses.
RBAC
See who can do what across accounts, roles, and bindings.
Helm
Manage repositories and Helm releases from the GUI.
Port Forward & DNS
Forward ports and register automatic local DNS entries.
Debug Assistant
Launch an ephemeral debug pod with the tools you need.
Custom Resources
Discover CRDs and browse or edit their instances as YAML.
Dashboard
Open the Kubernetes overview to see a live summary of the cluster: node count and status, running and pending pods, deployments, services, and the most recent cluster events. Use the dashboard as a starting point before drilling into specific resources.
Two ways to start
Open Cluster and use the Start a local cluster with k3d flow when you want a disposable local cluster for development or testing.
Open Cluster and use the Import an existing cluster flow when you already have a kubeconfig for kind, minikube, EKS, GKE, AKS, or on-prem.
Namespaces
Use the namespace switcher in the top bar to scope every Kubernetes list. Switch namespaces without disconnecting from the cluster, then keep browsing workloads, networking, config, and RBAC in the new namespace.
What's not yet supported
Phase 1 focuses on the resources above. You do not get these workflows yet:
- Cluster creation outside k3d, such as kubeadm or managed-service provisioning.
- Horizontal pod autoscalers.
- Gateway API beyond Ingress.
- Visual CRD editors, use YAML editing instead.