Difficulty: Beginner
Estimated Time: 15 minutes

This scenario explores the basic techniques for observing the state of Kubernetes using metrics.

In the following steps you will learn how to:

  • access metrics information produced by each cAdvisor in each Kubelet,
  • inspect resources using the Resource Metrics API,
  • viewing metrics reported by Metrics Server.

The scenario introduced some fundamental techniques to inspecting a cluster and its control plane components. Additional topics on observability related to logging, tracing, or monitoring with Prometheus are covered in other scenarios.

Lessons Learned

With these steps you have learned how to:

  • ✔ access metrics information produced by each cAdvisor in each Kubelet,
  • ✔ inspect resources using the Resource Metrics API,
  • ✔ viewing metrics reported by Metrics Server.

For a deeper understanding of these topics and more join
Jonathan Johnson
at various conferences, symposiums, workshops, and meetups.

Software Architectures ★ Speaker ★ Workshop Hosting ★ Kubernetes & Java Specialist

Basic Kubernetes Observability

Step 1 of 5

Your Kubernetes Cluster

For this scenario, Katacoda has just started a fresh Kubernetes cluster for you. Verify it's ready for your use.

kubectl version --short && \ kubectl get componentstatus && \ kubectl get nodes && \ kubectl cluster-info

The Helm package manager used for installing applications on Kubernetes is also available.

helm version --short

Kubernetes Dashboard

You can administer your cluster with the kubectl CLI tool or use the visual Kubernetes Dashboard. Use this script to access the protected Dashboard.

token.sh