lab002.md

Lab 2: Review the Kubernetes environment

For the sake of time, some of the required setup has already been taken care of. The following steps were performed as part of the instance preparation:

• Installed Kubernetes prerequisites
• Deployed an all-in-one Kubernetes cluster using kubeadm
• Deployed all the networking components:
  • Deployed Flannel
  • Deployed Multus CNI
  • Deployed OVS CNI
• Deployed local volumes provisioner
• Deployed Prometheus Operator
  • Prometheus with its components
  • Grafana
• Resource manifests to interact with KubeVirt components have been copied over to your $HOME/student-materials

DISCLAIMER: This header is just for our own purpose, then you don't need execute it!:

mdsh-lang-bash() { shell; }

Verify the cluster

Let's ask the cluster for its status:

## LAB 002

kubectl version

• Output:

Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.3", GitCommit:"5e53fd6bc17c0dec8434817e69b04a25d8ae0ff0", GitTreeState:"clean", BuildDate:"2019-06-06T01:44:30Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.3", GitCommit:"5e53fd6bc17c0dec8434817e69b04a25d8ae0ff0", GitTreeState:"clean", BuildDate:"2019-06-06T01:36:19Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}

Now let's check that persistent volumes are ready and available:

kubectl get pv

• Output:

NAME                CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS      CLAIM   STORAGECLASS    REASON   AGE
local-pv-234582fe   5109Mi     RWO            Delete           Available           local-volumes            2d
local-pv-5d33c489   5109Mi     RWO            Delete           Available           local-volumes            2d
local-pv-6035a584   5109Mi     RWO            Delete           Available           local-volumes            2d
local-pv-a56cebb5   5109Mi     RWO            Delete           Available           local-volumes            2d

And finally, let's check that Prometheus and Grafana are running and exposed:

kubectl get all -n prometheus

• Output:

NAME                                                         READY   STATUS    RESTARTS   AGE
pod/alertmanager-kubevirtlab-prometheus-ope-alertmanager-0   2/2     Running   0          2d
pod/kubevirtlab-grafana-bf9db4bd9-r8pmt                      2/2     Running   0          2d
pod/kubevirtlab-kube-state-metrics-6544b5778c-gvqc9          1/1     Running   0          2d
pod/kubevirtlab-prometheus-node-exporter-8dp4d               1/1     Running   0          2d
pod/kubevirtlab-prometheus-ope-operator-78d5bbf8ff-rx9kv     1/1     Running   0          2d
pod/prometheus-kubevirtlab-prometheus-ope-prometheus-0       3/3     Running   0          2d

NAME                                              TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)             AGE
service/alertmanager-operated                     ClusterIP   None             <none>        9093/TCP,6783/TCP   2d
service/kubevirtlab-grafana                       ClusterIP   10.96.1.202      <none>        80/TCP              2d
service/kubevirtlab-grafana-nodeport              NodePort    10.111.14.110    <none>        3000:30300/TCP      2d
service/kubevirtlab-kube-state-metrics            ClusterIP   10.101.96.232    <none>        8080/TCP            2d
service/kubevirtlab-prometheus-node-exporter      ClusterIP   10.99.86.74      <none>        9100/TCP            2d
service/kubevirtlab-prometheus-ope-alertmanager   ClusterIP   10.105.253.180   <none>        9093/TCP            2d
service/kubevirtlab-prometheus-ope-operator       ClusterIP   10.109.209.37    <none>        8080/TCP            2d
service/kubevirtlab-prometheus-ope-prometheus     NodePort    10.109.224.249   <none>        9090:30090/TCP      2d
service/prometheus-operated                       ClusterIP   None             <none>        9090/TCP            2d

NAME                                                  DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
daemonset.apps/kubevirtlab-prometheus-node-exporter   1         1         1       1            1           <none>          2d

NAME                                                  READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/kubevirtlab-grafana                   1/1     1            1           2d
deployment.apps/kubevirtlab-kube-state-metrics        1/1     1            1           2d
deployment.apps/kubevirtlab-prometheus-ope-operator   1/1     1            1           2d

NAME                                                             DESIRED   CURRENT   READY   AGE
replicaset.apps/kubevirtlab-grafana-bf9db4bd9                    1         1         1       2d
replicaset.apps/kubevirtlab-kube-state-metrics-6544b5778c        1         1         1       2d
replicaset.apps/kubevirtlab-prometheus-ope-operator-78d5bbf8ff   1         1         1       2d

NAME                                                                    READY   AGE
statefulset.apps/alertmanager-kubevirtlab-prometheus-ope-alertmanager   1/1     2d
statefulset.apps/prometheus-kubevirtlab-prometheus-ope-prometheus       1/1     2d

Notice that both PromUI and Grafana have been exposed on the node's TCP ports 30090 and 30300. Both can be accessed with the following details:

• PromUI
  • http://kubevirtlab-<number>.try.kubevirt.me:30090
• Grafana
  • http://kubevirtlab-<number>.try.kubevirt.me:30300
  • Username: admin
  • Password: kubevirtlab123

Recap

• We've reviewed the available PVs in the cluster that we'll use later on
• We've reviewed the Prometheus deployment, Grafana and PromUI services exposed on the node

This concludes this section of the lab.

<< Previous: Introduction / Connectivity | README | Next: Deploy KubeVirt/CDI/UI >>