Repository navigation
Commit 3d60a29
committed
fix(apps/kubernetes): bump Cilium HR install timeout 10m -> 15m
The tenant Cilium HR's `spec.timeout: 10m` races the image pull to a
fresh Talos worker VM on CI runners. Analysis of cozyreport artifact
from the E2E run 28843794670 (job 85543970802) on the `kubernetes-
previous` test:
- Every Cilium init container on the tenant node is stuck with
`state: waiting, reason: PodInitializing` and `imageID: ""` — kubelet
is still fetching `iad.ocir.io/.../cozystack/cilium:main@sha256:...`
when the 10m HR install timeout fires.
- `cilium-agent`'s `current.log` and `previous.log` are both zero
bytes — the container never entered the running phase.
- On the same run, `kubernetes-latest` (v1.35.6) took 13:10 wall-clock
and passed; `kubernetes-previous` (v1.34.9) took 13:52 and failed.
Both minors sit right on the edge of the 10m HR budget; whichever
test races the pull first wins. The delta is not version-specific.
15m matches the tenant Kubernetes install budget already used by the
outer HR and by the monitoring chart's cozyrds annotation. Cilium's
install work itself completes in seconds — the extra headroom is
purely to absorb slow first-time image pulls on runners without a
warm mirror cache.
Closes #3229.
Signed-off-by: IvanHunters <[email protected]>1 parent 0f55a15 commit 3d60a29
1 file changed
Lines changed: 6 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
44 | 44 | | |
45 | 45 | | |
46 | 46 | | |
47 | | - | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
48 | 53 | | |
49 | 54 | | |
50 | 55 | | |
| |||
0 commit comments