$ kubectl get nodes

NAME STATUS ROLES AGE VERSION

minikube Ready master 19m v1.10.0



$ kubectl describe nodes minikube

Name: minikube

Roles: master

Labels: beta.kubernetes.io/arch=amd64

beta.kubernetes.io/os=linux

kubernetes.io/hostname=minikube

node-role.kubernetes.io/master=

Annotations: node.alpha.kubernetes.io/ttl=0

volumes.kubernetes.io/controller-managed-attach-detach=true

Taints: <none>

CreationTimestamp: Fri, 20 Apr 2018 02:05:02 +0800

Conditions:

Type Status LastHeartbeatTime LastTransitionTime Reason Message

---- ------ ----------------- ------------------ ------ -------

OutOfDisk False Fri, 20 Apr 2018 02:24:25 +0800 Fri, 20 Apr 2018 02:04:44 +0800 KubeletHasSufficientDisk kubelet has sufficient disk space available

MemoryPressure False Fri, 20 Apr 2018 02:24:25 +0800 Fri, 20 Apr 2018 02:04:44 +0800 KubeletHasSufficientMemory kubelet has sufficient memory available

DiskPressure False Fri, 20 Apr 2018 02:24:25 +0800 Fri, 20 Apr 2018 02:04:44 +0800 KubeletHasNoDiskPressure kubelet has no disk pressure

PIDPressure False Fri, 20 Apr 2018 02:24:25 +0800 Fri, 20 Apr 2018 02:04:44 +0800 KubeletHasSufficientPID kubelet has sufficient PID available

Ready True Fri, 20 Apr 2018 02:24:25 +0800 Fri, 20 Apr 2018 02:04:44 +0800 KubeletReady kubelet is posting ready status

Addresses:

InternalIP:

Hostname: minikube

Capacity:

cpu: 2

ephemeral-storage: 16888216Ki

hugepages-2Mi: 0

memory: 2048052Ki

pods: 110

Allocatable:

cpu: 2

ephemeral-storage: 15564179840

hugepages-2Mi: 0

memory: 1945652Ki

pods: 110

System Info:

Machine ID: 43326e10eee04511b72c5b8e937483b3

System UUID: 1A90BACA-DC70-4DFB-9540-A38C5C37A12B

Boot ID: 2101ef66-2569-4f84-a2c4-9bba07e07614

Kernel Version: 4.9.64

OS Image: Buildroot 2017.11

Operating System: linux

Architecture: amd64

Container Runtime Version: docker://17.12.1-ce

Kubelet Version: v1.10.0

Kube-Proxy Version: v1.10.0

ExternalID: minikube

Non-terminated Pods: (9 in total)

Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits

--------- ---- ------------ ---------- --------------- -------------

kube-system etcd-minikube 0 (0%) 0 (0%) 0 (0%) 0 (0%)

kube-system kube-addon-manager-minikube 5m (0%) 0 (0%) 50Mi (2%) 0 (0%)

kube-system kube-apiserver-minikube 250m (12%) 0 (0%) 0 (0%) 0 (0%)

kube-system kube-controller-manager-minikube 200m (10%) 0 (0%) 0 (0%) 0 (0%)

kube-system kube-dns-86f4d74b45-rn77t 260m (13%) 0 (0%) 110Mi (5%) 170Mi (8%)

kube-system kube-proxy-54grl 0 (0%) 0 (0%) 0 (0%) 0 (0%)

kube-system kube-scheduler-minikube 100m (5%) 0 (0%) 0 (0%) 0 (0%)

kube-system kubernetes-dashboard-5498ccf677-76m4p 0 (0%) 0 (0%) 0 (0%) 0 (0%)

kube-system storage-provisioner 0 (0%) 0 (0%) 0 (0%) 0 (0%)

Allocated resources:

(Total limits may be over 100 percent, i.e., overcommitted.)

CPU Requests CPU Limits Memory Requests Memory Limits

------------ ---------- --------------- -------------

815m (40%) 0 (0%) 160Mi (8%) 170Mi (8%)

Events:

Type Reason Age From Message

---- ------ ---- ---- -------

Normal NodeHasSufficientPID 19m (x5 over 19m) kubelet, minikube Node minikube status is now: NodeHasSufficientPID

Normal NodeAllocatableEnforced 19m kubelet, minikube Updated Node Allocatable limit across pods

Normal NodeHasSufficientDisk 19m (x6 over 19m) kubelet, minikube Node minikube status is now: NodeHasSufficientDisk

Normal NodeHasSufficientMemory 19m (x6 over 19m) kubelet, minikube Node minikube status is now: NodeHasSufficientMemory

Normal NodeHasNoDiskPressure 19m (x6 over 19m) kubelet, minikube Node minikube status is now: NodeHasNoDiskPressure

Normal Starting 19m kube-proxy, minikube Starting kube-proxy

NOTE:

There are two types of kubernetes system components:

Those that run in a container (e.g: kubernetes scheduler and kube-proxy run in a container) Those that do not run in a container (e.g: kubelet and container runtime, for example Docker, do not run in containers.)

One of the interesting aspects of Kubernetes is that many of the components that make up the Kubernetes cluster are actually deployed using Kubernetes itself.

All of these components run in the kube-system namespace.

A Namespace in Kubernetes is an entity for organising Kubernetes resources. You can think of it like a folder in a filesystem.

Cluster Components (kube-proxy, kube-dns, kubernetes-dashboard)

Please take note the followings from Step 7 output:

Internal IP.

How many pods we can handle.

Container Runtime.

Kubelet Version: v1.10.0

Kube-Proxy Version: v1.10.0

Step 8 — Explore Kubernetes Docker Container Images and Processes.