Kubernetes Resource Operations: From Inspection to Action

Managing Kubernetes resources typically requires multiple commands and context switches. Kunobi streamlines this into a single interface.

Managing Kubernetes resources usually means: get the YAML, save to file, edit, apply, verify. Five commands for one change. Kunobi does this in a single interface—find the resource, edit it, save, done.

The Typical Workflow

kubectl get deployment my-app -o yaml > deployment.yaml
vim deployment.yaml
kubectl apply -f deployment.yaml
kubectl get deployment my-app -o yaml  # verify

Four commands, intermediate files, multiple context switches.

In Kunobi:

Navigate to the deployment
Open the YAML editor
Edit and save

The resource updates immediately. No temp files, no switching between terminals.

What You Can Do

View Resources

Each resource shows status, metadata, labels, annotations, and ownership in one panel. Pods display container status, restart counts, and resource usage. Deployments show replica state and rollout status. Information you'd normally get from multiple describe and get commands, all in one view.

Edit Resources

Full YAML editing with syntax highlighting. Validation catches errors before they hit the API server.

For common tasks, you don't need YAML. Scale deployments with a replica count field. Update environment variables through structured inputs. The UI adapts to the resource type.

Create Resources

Paste YAML from docs, Helm outputs, or templates. Kunobi applies it to the current namespace and context. Useful for testing new definitions or deploying examples.

Delete Resources

Deletion shows a confirmation with resource type, name, namespace, and cluster. Clear context prevents accidental deletions in the wrong environment.

Real-Time Updates

Changes appear immediately. Scale from 3 to 5 replicas and watch new pods show up in the list. Delete a pod and see the replacement appear as the controller recreates it.

No polling, no manual refresh. You see what's happening as it happens.

Safeguards

Every modification requires confirmation. You see what will change before committing.

Cluster and namespace are always visible. You know exactly where you are before making changes.

Use Cases

Incidents: Quick iteration from diagnosis to fix
Development: Fast config adjustments without terminal switching
Multi-environment: Clear context indicators prevent cross-environment mistakes
Learning: Safe environment to experiment and observe behavior

Try It

Connect to a cluster, make a change, see the result.

Download Kunobi