Fixing a kubelet memory leak in Kubernetes 1.36

Kubernetes 1.36 contains a critical memory leak in the kubelet component caused by unreleased Go contexts during pod synchronization operations, which can cause node memory exhaustion and pod restarts even on resource-constrained systems. This regression poses a significant operational risk for production Kubernetes deployments, potentially impacting cluster stability and requiring immediate patching once available. IT organizations running Kubernetes 1.36 should prioritize monitoring kubelet memory usage and prepare contingency plans, while the community works toward a fix for this lifecycle management bug.