Hands-on Lab·Certified Kubernetes Security Specialist
Container Scanning and Vulnerability Staleness
A vulnerability scan is a timestamped claim about an image, not a property of it. This guide reads what one actually reports, shows why most of it cannot be acted on, and turns it into a build gate that a team will not immediately disable.
Supply Chain Security Guide 27 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 15 min
Trivy's vulnerability database is downloaded and cached with an explicit UpdatedAt and NextUpdate, which is what makes the shelf life measurable rather than theoretical.
- 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 when a scan result has to mean something. This matters because a scan is a timestamped claim rather than a property of the image - the same image scanned tomorrow gives a different answer.
- reading what a scan actually reports, and how much of it is genuinely actionable
- finding the date on the answer, in the database sitting behind the result
- turning it into a gate with exit codes, and the flag that makes them usable
Before you start
- guide 25 - where these findings come from.
-
What a scan actually reports
-
The answer has a date on it
-
Making it a gate