### Which jobs are flaking?

https://storage.googleapis.com/k8s-triage/index.html?sig=windows&text=should%20not%20exceed%20limit%20by%20%3E%205%25

### Which tests are flaking?
```
Kubernetes e2e suite: [It] [sig-windows] [Feature:Windows] Cpu Resources [Serial] Container limits should not be exceeded after waiting 2 minutes
```

Failed error:
```
[FAILED] Pod cpu-resources-test-windows-183/cpulimittest-091cc328-6d0d-4984-ac14-c6c63edea2dd reported usage is 0.525644525, but it should not exceed limit by > 5%
```
### Since when has it been flaking?

Since migration to containerd 1.7.x

### Testgrid link

https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-capz-1-28-windows-serial-slow/1782880261759832064

### Reason for failure (if possible)

_No response_

### Anything else we need to know?

The expected cpu usage is set to 0.5, but the actual cpu usage could be around 0.52-0.6, hence exceeding the limit more than the threshold of 5%. 

### Relevant SIG(s)

/sig windows
Cpu Resources Container limits test is flaky for Windows on containerd 1.7
This is a GitHub Issue
repo:kubernetes
owner:kubernetes
Title : Cpu Resources Container limits test is flaky for Windows on containerd 1.7
Issue date:

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

https://storage.googleapis.com/k8s-triage/index.html?sig=windows&text=should%20not%20exceed%20limit%20by%20%3E%205%25

### Which tests are flaking?
```
Kubernetes e2e suite: [It] [sig-windows] [Feature:Windows] Cpu Resources [Serial] Container limits should not be exceeded after waiting 2 minutes
```

Failed error:
```
[FAILED] Pod cpu-resources-test-windows-183/cpulimittest-091cc328-6d0d-4984-ac14-c6c63edea2dd reported usage is 0.525644525, but it should not exceed limit by > 5%
```
### Since when has it been flaking?

Since migration to containerd 1.7.x

### Testgrid link

https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-capz-1-28-windows-serial-slow/1782880261759832064

### Reason for failure (if possible)

_No response_

### Anything else we need to know?

The expected cpu usage is set to 0.5, but the actual cpu usage could be around 0.52-0.6, hence exceeding the limit more than the threshold of 5%. 

### Relevant SIG(s)

/sig windows
--- end body ---
