Kubernetes 1.29 Emeritus Advisor announced upcoming changes to the structure of the release team. Beginning with the 1.30 release cycle, the Bug Triage and CI Signal teams will be merged into a singular team called “Release Signal”.
The K8s Contributor Summit Europe 2024 still has open positions for interested volunteers.
The WG batch leads were updated this week.
Next Deadline: Themes and Docs Complete, November 28
Hopefully, you’ve debugged all of your features and are hard at work editing documentation, because those docs need to be edited and done in a week. Then on to the release! Please keep an eye out for and respond to any test failures during code freeze, as always.
This KEP proposes allowing emitting of SLI (Service Level Indicator) data in a structured manner. This is so that monitoring agents can scrape this data more frequently and create SLOs (Service Level Objects) and alerts based on these SLIs. The proposed solution for this is to add a new endpoint on Kubernetes components
/metrics/slis which would return the SLI data in Prometheus format. This would help create a uniform interface by which we can consume health checking information and would allow SLIs to be created without a specialized monitoring agent.
This KEP was in alpha in the v1.26 release, and is currently tracked graduate to stable in the upcoming v1.29 release.
Last Week In Kubernetes Development (LWKD) is a product of multiple contributors participating in Kubernetes SIG Contributor Experience. All original content is licensed Creative Commons Share-Alike, although linked content and images may be differently licensed. LWKD does collect some information on readers, see our privacy notice for details.
You may contribute to LWKD by submitting pull requests or issues on the LWKD github repo.