### Which jobs are flaking?

master-informing

capz-windows-master

### Which tests are flaking?

ci-kubernetes-e2e-capz-master-windows.Overall

### Since when has it been flaking?

It's been failing consecutively since 5/29. Even when the test shows up green, if you click on it, it shows that it still couldn't find the secret.

### Testgrid link

https://testgrid.k8s.io/sig-release-master-informing#capz-windows-master

### Reason for failure (if possible)

Error: "capz-conf-etj4t6-kubeconfig" not found in namespace "default": secrets "capz-conf-etj4t6-kubeconfig" not found

### Anything else we need to know?

It looks to me like Azure Identity isn't creating an appropriate secret that's needed.

### Relevant SIG(s)

/sig-windows

@kubernetes/release-team-release-signal
[Flaking Test] ci-kubernetes-e2e-capz-master-windows.Overall
This is a GitHub Issue
repo:kubernetes
owner:kubernetes
Title : [Flaking Test] ci-kubernetes-e2e-capz-master-windows.Overall
Issue date:

--- start body ---
### Which jobs are flaking?

master-informing

capz-windows-master

### Which tests are flaking?

ci-kubernetes-e2e-capz-master-windows.Overall

### Since when has it been flaking?

It's been failing consecutively since 5/29. Even when the test shows up green, if you click on it, it shows that it still couldn't find the secret.

### Testgrid link

https://testgrid.k8s.io/sig-release-master-informing#capz-windows-master

### Reason for failure (if possible)

Error: "capz-conf-etj4t6-kubeconfig" not found in namespace "default": secrets "capz-conf-etj4t6-kubeconfig" not found

### Anything else we need to know?

It looks to me like Azure Identity isn't creating an appropriate secret that's needed.

### Relevant SIG(s)

/sig-windows

@kubernetes/release-team-release-signal
--- end body ---
