kubernetes : kubectl useful commands

Working through the interactive tutorial here is a good reference for kubectl usage.

A few notes for reference:

Copy master node config to a remote machine (from here):

scp root@<master ip>:/etc/kubernetes/admin.conf .

All of the commands if running on a remote machine can use the copied conf file by passing: --kubeconfig ./admin.conf

Query nodes in the cluster:

kubectl get nodes


Show current cluster info:

./kubectl cluster-info

Kubernetes master is running at https://192.168.1.80:6443

KubeDNS is running at https://192.168.1.80:6443/api/v1/namespaces/kube-system/services/kube-dns/proxy

From the interactive tutorial:

Run kubernetes-bootcamp:

kubectl run kubernetes-bootcamp --image=docker.io/jocatalin/kubernetes-bootcamp:v1 --port=8080

Pods:

kubectl get pods
kubectl describe pod podname
kubectl delete pod podname

Deployments:

kubectl get deployments
kubectl describe deployment deploymentname
kubectl delete deployment deploymentname

Get logs

kubectl logs podname

HP iLO Integrated Remote Control Java Web Start App

I love that I can power on my HP DL380 server remotely using the iLO feature (it’s upstairs in my office). I hadn’t yet played with the ‘Integrated Remote Control’ yet though which is available from a link from the iLO home page. The Java Web Start version runs ok from Firefox which allows you to watch the start up process remotely and interact with the server startup menus.

After ESXi has completed booting, apparently you need an additional license to continue to use it past that point. At this point after ESXi there’s not much you can do with the server anyway so this is not a big deal (since interacting with ESXi is all via the web app).

Updating VMware ESXI Host Client via the Host Client web ui

After logging on to the ESXI host client web ui, the Unhandled Exception dialog has started to bug me, but I think it’s fixed in a patch release since when I first installed ESXI 6.5.

This how-to doc describes the steps for updating the Host Client using the Host Client web ui itself, via Host / Manage / Packages / Install Update and pasting the URL to the current/latest .vib file which you can get from here.

The Unhandled Exception issue described here is now fixed – the specific update I installed was:

http://download3.vmware.com/software/vmw-tools/esxui/esxui-signed-7119706.vib