Termiyo
← All solutions

Solutions

Kubernetes pods and deployments

Check a cluster and scale a deployment without typing kubectl, and see the exact command before anything changes.

Termiyo’s Kubernetes view uses the kubectl and kubeconfig you already have to list a cluster’s pods and deployments, follow a pod’s log, open a shell in a container, and scale a deployment after showing you the exact kubectl command. Listing only reads. Use it to check a cluster, or make a small change, without typing kubectl.

Termiyo uses the kubectl and kubeconfig you already have. Listing is read-only; a change such as scaling a deployment shows you the exact command and runs only when you say so.

Recorded in Termiyo with a stand-in for kubectl written for the recording, answering for a demo cluster. No real cluster or kubeconfig is used.

Steps

  1. Open the Kubernetes view

    In “All tools”, open “Containers” and choose “Kubernetes”. Pick the “Context” and a “Namespace”, or “All namespaces”; the pods are listed with their state and containers.

  2. Follow a pod’s log

    Press “Container log” on a pod to follow its first container’s log in a new terminal, or press a container’s name to open a shell in it.

  3. Scale a deployment

    Choose “Deployments”, press “Scale” on one, set the number of replicas and press “Review”. Termiyo shows the exact kubectl line under “Check the command”; “Run it” runs it.

Good to know

  • On a context marked production, opening a shell or a log, scaling and restarting ask you to type the context’s name first.
  • If kubectl is not installed, the panel offers to put the official build in a folder of its own, checked against its published SHA-256.

Transcript

Check a cluster and scale a deployment without typing kubectl, and see the exact command before anything changes.

Open Kubernetes, and the cluster’s pods are listed, read from the kubeconfig you already have.

Follow a pod’s log, without looking up its name.

To scale a deployment, set the replicas and review. The exact kubectl command comes first, and nothing changes until you run it.