# CI Signal Report for Week 9, Release cycle 1.27, 2023-03-09, 🟢

Hello and welcome to the CI Signal report for the [Kubernetes 1.27 release cycle](https://github.com/kubernetes/sig-release/tree/master/releases/release-1.27). This is week 9 of the release cycle.

The CI Signal team observes closely
- [master-blocking](https://testgrid.k8s.io/sig-release-master-blocking#Summary)
- [master-informing](https://testgrid.k8s.io/sig-release-master-informing#Summary)

Next release cut v1.27.0-beta.0 is planned on Thursday 2023-03-16. This is after CODE FREEZE which is scheduled for next Tuesday 2023-03-14. Expect to see a message in `#release-ci-signal` to give a [go or no-go signal](https://github.com/kubernetes/sig-release/blob/master/release-team/role-handbooks/ci-signal/README.md#release-cutting---go-or-no-go) from CI Signal Shadow [@gracenng](https://github.com/gracenng).

Overall our status is 🟢 Green.

We have open issues related to master-informing dashboard flakes which have all been triaged by their respective SIGs or are waiting on a fix to be merged. As these are flakes and on the master-informing dashboard, these are tolerable for the release.

This week we investigated:
- issue related to changes in the bucket retention policy that affected several tests, github issues [#116229](https://github.com/kubernetes/kubernetes/issues/116229) and [#116224](https://github.com/kubernetes/kubernetes/issues/116224), [slack thread](https://kubernetes.slack.com/archives/CN0K3TE2C/p1677757427497919).
  - THANK YOU to [@liggitt](https://github.com/liggitt) and [@ameukam](https://github.com/ameukam) for your triage and quick attention to this issue!

For more information and the latest state visit the [CI Signal Project board](https://github.com/orgs/kubernetes/projects/68/).

Also see attached 2023-03-09-report.md.

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