An attacker with read access to a Kubernetes cluster's etcd database wants to compromise node-level runtimes. What high-value secret stored within etcd presents the most immediate risk of allowing cluster-wide node takeover if extracted?
Trap 1: Internal DNS records for CoreDNS
CoreDNS records map names to IPs but do not inherently provide cryptographic authentication material.
Trap 2: HorizontalPodAutoscaler metric configurations
HPA configs contain scaling targets, not sensitive credential material.
Trap 3: PersistentVolume claim capacity metadata
PVC metadata describes storage size and access modes, lacking credential value.
- A
ServiceAccount tokens with high-privilege clusterrole bindings
Service account tokens stored in secrets provide direct authentication to the Kubernetes API server, allowing an attacker to impersonate that service account and leverage its clusterrole bindings.
- B
Internal DNS records for CoreDNS
Why wrong: CoreDNS records map names to IPs but do not inherently provide cryptographic authentication material.
- C
HorizontalPodAutoscaler metric configurations
Why wrong: HPA configs contain scaling targets, not sensitive credential material.
- D
PersistentVolume claim capacity metadata
Why wrong: PVC metadata describes storage size and access modes, lacking credential value.