Differences between revisions 2 and 3

kubernetes

https://www.katacoda.com/courses/kubernetes
minikube version # check version 1.2.0
minikube start

   1 $ minikube version
   2 minikube version: v1.2.0
   3 $ minikube start
   4 * minikube v1.2.0 on linux (amd64)
   5 * Creating none VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
   6 * Configuring environment for Kubernetes v1.15.0 on Docker 18.09.5
   7   - kubelet.resolv-conf=/run/systemd/resolve/resolv.conf
   8 * Pulling images ...
   9 * Launching Kubernetes ...
  10 
  11 * Configuring local host environment ...
  12 * Verifying: apiserver proxy etcd scheduler controller dns
  13 * Done! kubectl is now configured to use "minikube"

cluster details and health status

   1 $ kubectl cluster-info
   2 Kubernetes master is running at https://172.17.0.30:8443
   3 KubeDNS is running at https://172.17.0.30:8443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
   4 
   5 To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

get cluster nodes

   1 $ kubectl get nodes
   2 NAME       STATUS   ROLES    AGE    VERSION
   3 minikube   Ready    master   3m1s   v1.15.0

-  ⇤ ← Revision 2 as of 2019-07-27 15:55:03 → 
  Size: 648
  Editor: localhost
  Comment:
+   ← Revision 3 as of 2019-07-27 15:57:22 → ⇥
  Size: 1153
  Editor: localhost
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 20:
+== cluster details and health status ==
{{{#!highlight bash
$ kubectl cluster-info
Kubernetes master is running at https://172.17.0.30:8443
KubeDNS is running at https://172.17.0.30:8443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
}}}

== get cluster nodes ==
{{{#!highlight bash
$ kubectl get nodes
NAME       STATUS   ROLES    AGE    VERSION
minikube   Ready    master   3m1s   v1.15.0
}}}