Kubernetes 1.35 Introduces Structured JSON Responses for z-pages Debugging Endpoints
The release of Kubernetes 1.35 introduces significant enhancements to its debugging capabilities through updated z-pages APIs. Previously introduced as an alpha feature in version 1.32, z-pages provide runtime diagnostics for critical control plane components such as kube-apiserver, kube-controller-manager, and kube-scheduler. While these endpoints were valuable for human operators, they originally returned plain text output that was difficult to parse programmatically. The new update addresses this limitation by adding support for structured, versioned JSON responses for both /statusz and /flagz endpoints. This change enables developers to build automated tooling and streamline troubleshooting workflows by providing machine-parseable data. Crucially, the update maintains backward compatibility; the endpoints continue to return plain text by default unless a specific Accept header is included in the request. This design ensures existing workflows remain unaffected while offering advanced options for modern automation needs. The structured responses include detailed metadata, version information, and uptime statistics in a standardized format, marking a step forward in operational observability for Kubernetes clusters.
Wire timeline
Kubernetes 1.35 Introduces Structured JSON Responses for z-pages Debugging Endpoints
The release of Kubernetes 1.35 introduces significant enhancements to its debugging capabilities through updated z-pages APIs. Previously introduced as an alpha feature in version 1.32, z-pages provide runtime diagnostics for critical control plane components such as kube-apiserver, kube-controller-manager, and kube-scheduler. While these endpoints were valuable for human operators, they originally returned plain text output that was difficult to parse programmatically. The new update addresses this limitation by adding support for structured, versioned JSON responses for both /statusz and /flagz endpoints. This change enables developers to build automated tooling and streamline troubleshooting workflows by providing machine-parseable data. Crucially, the update maintains backward compatibility; the endpoints continue to return plain text by default unless a specific Accept header is included in the request. This design ensures existing workflows remain unaffected while offering advanced options for modern automation needs. The structured responses include detailed metadata, version information, and uptime statistics in a standardized format, marking a step forward in operational observability for Kubernetes clusters.
Kubernetes Blog