Hands-on Lab·Certified Kubernetes Security Specialist
Assessing Cluster Detection Coverage
Every guide in this domain changed something and then put it back. This one counts what is left, which is the same set of commands you should run against a cluster you have just inherited.
Monitoring and Runtime Guide 38 of 40 Intermediate
- Kubernetesapiserver v1.36.4, kubelet v1.36.3
- Runtimecontainerd 2.2.6
- CNICilium 1.18.1
- Built withkubeadm v1.36.3
- TimeAbout 14 min
Read-only. Every command here can be run against a production cluster without changing anything.
- Host kernel7.0.0-29
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| CKA6001 | 192.168.0.46 | Ubuntu 26.04 LTS | Control Plane Node (tainted NoSchedule) | 2 Core | 4 GB | 50 GB |
| CKA6001-NODE01 | 192.168.0.47 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA6001-NODE02 | 192.168.0.48 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
This guide includes
Use this at the end of the domain, because every guide in it changed something and then put it back. This matters because the honest question is what the cluster detects now - and that is measurable, control by control.
- taking an inventory of six controls, one line each
- reading what the one working detector gives you, and precisely what it does not
- counting the posture of everything running, four different ways
- scoring the domain's own competency list against the machine
Before you start
- guide 37 - the layers this page is counting.
-
The inventory
-
What the one working detector gives you
-
The posture of what is running
-
The scoreboard, competency by competency