EKS: mark pause-container as pinned in containerd
Bug #2061187 reported by
Robby Pocase
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
New
|
Medium
|
Unassigned |
Bug Description
LP:2060537 pointed out that in EKS 1.29 the pause container is being pruned by garbage collection. This has had a workaround provided via a periodic cron poll. Longer term, we should update the containerd configuration to pin the pause container [1] at launch. This will avoid the container being pruned entirely.
[0] - https:/
[1] - https:/
To post a comment you must log in.
Can we get any update here? The workaround is fine, but with highly multi-tenant and short-lived workloads we still encounter periods where the pause container is garbage collected.
edit: additionally, we tried to shim-in a public image by adding `[env, PAUSE_CONTAINER _IMAGE= registry. k8s.io/ pause, /etc/eks/ bootstrap. sh`, ...] to our cloud-init config, but there's an error from the script that pulls the image down because it expects that the image is in ECR, not any arbitrary registry.