CI Signal Report for Week 10, Release cycle 1.27, 2023-03-18, 🟢

[Laura Lorenz]

Hello and welcome to the CI Signal report for the Kubernetes 1.27 release cycle. This is week 10 of the release cycle.

The CI Signal team observes closely

• master-blocking
• master-informing

TEST FREEZE, as well as the next release cut, is planned for next Tuesday 2023-03-21. As the release cut is in the next days, expect to see a message in #release-ci-signal to give a go or no-go signal from CI Signal Shadow @drewhagen.

Overall our status is 🟢 Green.

Thank you to SIG-Testing and especially @BenTheElder keeping the CI Signal team up to date on some ongoing test infra improvements.

By the way, if you are looking at testgrid dashboards for prior releases (blocking-1.25, blocking-1.26, etc), they are affected by an issue with a change in build tags, see github issue #2972.

This week we investigated:

• sig-release-master-informing, build-master, related to an issue in golang causing issues with linux/arm builds, github issue #116492
• sig-release-master-informing, kubeadm-kinder-upgrade-1-26-latest and kubeadm-kinder-latest, related to changes in kubectl explain output format expectations, github issue #116650
• sig-release-master-blocking, verify-master, related to deprecation of a beta API, github issue #116703, slack thread

Thank you @pacoxu, @liggit, @aojea, @alexzielenski and @lavalamp for your triage, quick attention and quick review of the fixes!

For more information and the latest state visit the CI Signal Project board.

This summary and the attached 2023-03-17-report.md are also available in this gist.

Questions or feedback? Reach us on Slack at #sig-release or #release-ci-signal. Thank you!