Kubernetes 1.35: Enhanced Debugging with Versioned z-pages APIs

Debugging Kubernetes control plane components can be challenging, especially when you need to quickly understand the runtime state of a component or verify its configuration. With Kubernetes 1.35, we're enhancing the z-pages debugging endpoints with structured, machine-parseable responses that make it easier to build tooling and automate troubleshooting workflows. What are z-pages? z-pages are special debugging endpoints exposed by Kubernetes control plane components. Introduced as an alpha feature in Kubernetes 1.32, these endpoints provide runtime diagnostics for components like kube-apiserver , kube-controller-manager , kube-scheduler , kubelet and kube-proxy . The name "z-pages" comes from the convention of using /*z paths for debugging endpoints. Currently, Kubernetes supports two primary z-page endpoints: /statusz Displays high-level component information including version information, start time, uptime, and available debug paths /flagz Shows all command-line arguments and their