A cluster runs on a managed Kubernetes service whose provider operates the control plane. Its worker nodes are virtual machines launched from the team's own launch template in an auto-scaling group the team created. A kernel flaw that enables container escape is announced. What should the team expect?
Choose one.
The shared-responsibility split can differ inside one cluster: managed control plane, customer-managed nodes.
Three facts combine. First, the kernel belongs to the worker nodes, not to the control plane. Second, nodes launched from the team's own launch template in its own auto-scaling group are a self-managed node group, so the team owns their patching even though the provider owns the control plane. Third, upgrading the cluster's Kubernetes version changes the control plane but does not replace the operating system of self-managed nodes. The tempting near-twin assumes the provider patches nodes, which is true for provider-managed node pools but not here.
- Place the vulnerability: the Linux kernel on the worker nodes.
- Work out who operates those nodes: launched from the team's own template, so self-managed.
- Assign the fix to that party, and remember that a control plane upgrade does not reach self-managed nodes.
Exam tip: Responsibility follows who operates each part: managed control plane is the provider's, self-managed nodes are yours.
KCSA: The 4Cs of Cloud Native Security, Infrastructure Security and Security Controls — the lesson that teaches this.