Repository navigation
Commit eebe586
authored
test(e2e): run tenant workers on one vCPU with CPU headroom above it (#3863)
## What this PR does
Moves the e2e tenant workers from two vCPUs to one, keeping a CPU limit
above the vCPU count: `resources.cpu: 1` with `podCpuLimit: 2` and
`podCpuRequest: 100m`.
This is the next step of the #3513 measurement
series. With two vCPUs the failing worker's two vCPU threads burn 1.4 to
1.8 cores between them while the guest kernel never gets past SMP
bringup, and raising the CFS ceiling from 2 to 3 cores (#3862) changed
neither the burn nor the progress, so the spin is between the two vCPUs
rather than against the quota. A single-vCPU guest has no sibling vCPU
to spin on, which is exactly what this shape tests. The ceiling of 2
keeps the QEMU emulator and IO threads from eating into the one core the
guest computes with, which was the failure shape of the original
single-vCPU workers whose quota equalled their vCPU count. The request
of 100m is what KubeVirt derived for a one-vCPU worker before, so
scheduling does not move.
Like its predecessors this changes only what the e2e suites run, not
what any chart ships by default.
### Screenshots
Not applicable, no UI change.
### Downstream repositories
The diff is one values block inside
`hack/e2e-chainsaw/_lib/run-kubernetes.sh`. Nothing in the trigger map
is touched.
- [x] No downstream repository is affected by this change
- [ ] [cozystack/website](https://github.com/cozystack/website) -
follow-up:
- [ ]
[cozystack/terraform-provider-cozystack](https://github.com/cozystack/terraform-provider-cozystack)
- follow-up:
- [ ]
[cozystack/ansible-cozystack](https://github.com/cozystack/ansible-cozystack)
- follow-up:
- [ ] [cozystack/ccp](https://github.com/cozystack/ccp) - follow-up:
- [ ] [cozystack/talm](https://github.com/cozystack/talm) - follow-up:
- [ ] [cozystack/cozyhr](https://github.com/cozystack/cozyhr) -
follow-up:
- [ ] [cozystack/cozy-proxy](https://github.com/cozystack/cozy-proxy) -
follow-up:
- [ ]
[cozystack/cozystack-telemetry-server](https://github.com/cozystack/cozystack-telemetry-server)
- follow-up:
- [ ]
[cozystack/external-apps-example](https://github.com/cozystack/external-apps-example)
- follow-up:
- [ ] [cozystack/examples](https://github.com/cozystack/examples) -
follow-up:
### Release note
```release-note
test(e2e): tenant workers in the kubernetes e2e suites run on one vCPU with a CPU limit of two, testing whether the node-join freeze is a spin between sibling vCPUs
```1 file changed
Lines changed: 11 additions & 11 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3167 | 3167 | | |
3168 | 3168 | | |
3169 | 3169 | | |
3170 | | - | |
3171 | | - | |
3172 | | - | |
| 3170 | + | |
| 3171 | + | |
| 3172 | + | |
| 3173 | + | |
| 3174 | + | |
| 3175 | + | |
3173 | 3176 | | |
3174 | 3177 | | |
3175 | 3178 | | |
3176 | 3179 | | |
3177 | 3180 | | |
3178 | 3181 | | |
3179 | | - | |
3180 | | - | |
3181 | | - | |
3182 | | - | |
3183 | | - | |
3184 | | - | |
3185 | | - | |
| 3182 | + | |
| 3183 | + | |
| 3184 | + | |
| 3185 | + | |
3186 | 3186 | | |
3187 | | - | |
| 3187 | + | |
3188 | 3188 | | |
3189 | 3189 | | |
3190 | 3190 | | |
| |||
0 commit comments