# CI Signal Report for Week 7, Release cycle 1.27, 2023-02-22, 🟢

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 7 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 is planned for next Tuesday, 2023-02-28. As the release cut is coming up, 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 @drewhagen.

Overall our status is 🟢 Green.
We are watching 3 flakes on the master-informing dashboard. As the master-informing dashboard is more tolerant to hosting flakes than the master-blocking dashboard, our status is currently green.

This week we are watching:
- [capz-windows-containerd-master](https://testgrid.k8s.io/sig-release-master-informing#capz-windows-containerd-master): `Kubernetes e2e suite.[It] [sig-windows] Services should be able to create a functioning NodePort service for Windows`, a known issue that has been reopened due to flakes reoccuring again, [kubernetes#98499](https://github.com/kubernetes/kubernetes/issues/98499). 
   - Thank you [@jsturtevant](https://github.com/jsturtevant) for triage! +kubernetes-sig-windows@googlegroups.com
- [gce-cos-master-serial](https://testgrid.k8s.io/sig-release-master-informing#gce-cos-master-serial):  `Kubernetes e2e suite.[It] [sig-storage] PersistentVolumes-local Stress with local volumes [Serial] should be able to process many pods and reuse local volumes`, which may be due to a cleanup race condition, [kubernetes#115945](https://github.com/kubernetes/kubernetes/issues/115945). 
   - Thank you [@msau42](https://github.com/msau42) for triage! +kubernetes-sig-storage@googlegroups.com
- [periodic-conformance-main-k8s-main](https://k8s-testgrid.appspot.com/sig-release-master-informing#periodic-conformance-main-k8s-main): `capa-e2e-conformance: [SynchronizedBeforeSuite]`, which may be due to a transient IAM issue, [kubernetes#115945](https://github.com/kubernetes/kubernetes/issues/115894). 
   - +kubernetes-sig-cluster-lifecycle@googlegroups.com

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

Attached: 2023-02-22-report.md

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