Hands-on Lab·Certified Kubernetes Security Specialist
Enabling Kubernetes Audit Logging
Every guide before this one changed something and nothing wrote down who did it. This is the change that fixes that: a policy file, five flags on the apiserver, and an honest look at the volume it produces.
Monitoring and Runtime Guide 32 of 40 Advanced
- 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 18 min
- Reviewed25 August 2026
Written against the versions above. apiserver v1.36.4 on a single-node kubeadm cluster. The policy is `audit.k8s.io/v1`, which has been stable since 1.12 and is what the exam uses.
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| CKA8001 | 192.168.0.56 | Ubuntu 26.04 LTS | Single Node (control plane, untainted) | 2 Core | 4 GB | 50 GB |
Before you start
- guide 20 - the same manifest, the same restart, the same recovery drill.
-
What this cluster records today
-
The policy, which is the whole design
-
Turn it on
-
The first thing it recorded