Hands-on Lab·Kubernetes and Cloud Native Security Associate
Image Scanning and Supply Chain Checks
Supply chain compliance asks two questions: what is in the thing you ship, and what is known to be wrong with it. An SBOM answers the first and a scanner answers the second. This guide runs both against a stale image and a minimal one, and reads what the answer depended on.
Compliance and Frameworks Guide 39 of 42 Intermediate
- Kubernetesapiserver v1.36.4, kubelet v1.36.3
- Runtimecontainerd 2.2.6
- CNICilium 1.18.1 - tunnel/VXLAN, with Hubble relay and UI
- Host OSUbuntu 26.04 LTS, kernel 7.0.0-29
- Built withkubeadm v1.36.3 - podSubnet 10.244.0.0/16, serviceSubnet 10.96.0.0/12
- TimeAbout 16 min
- Reviewed25 August 2026
Written against the versions above. Trivy 0.67.2, run as an ordinary Pod with no privilege. It fetches images from the registry itself and downloads a vulnerability database at run time, which is why the same scan can give a different answer tomorrow.
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| CKA5001 | 192.168.0.41 | Ubuntu 26.04 LTS | Control Plane Node (tainted NoSchedule) | 2 Core | 4 GB | 50 GB |
| CKA5001-NODE01 | 192.168.0.42 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA5001-NODE02 | 192.168.0.43 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA5001-NODE03 | 192.168.0.44 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
Before you start
-
One scanner, two images
-
A stale base image, by severity
-
Findings against components
-
The same scan against a minimal image
-
What the answer depended on