hashgraph / hashgraph/solo-weaver

fix(crio): ensure unreferenced image garbage collection period is long enough for prefetched images

Open
#1,025 0 comments 0 reactions 1 assignee Claimed by @leninmehedy View on GitHub
Improvement
Dominant language
Go
Stars
3
Forks
0
Avg merge
3d 5h
Merged PRs (30d)
47

Description

## Description

During network upgrade, the upgrade controller will prefetch consensus node images by launching a K8s job with an overridden entrypoint. The prefetched image will be unreferenced until the actual upgrade runs. We need to verify and configure the garbage collection period in both CRI-O and Kubelet so the unreferenced image is not garbage collected before it is needed.

## Acceptance Criteria

- [ ] Review the current CRI-O image GC settings configured by the provisioner
- [ ] Review the current Kubelet image GC settings configured by the provisioner
- [ ] Ensure the unreferenced image retention period is long enough to survive between prefetch (prepare phase) and actual upgrade (execute phase)
- [ ] Add or update configuration if the current GC period is too short
- [ ] Add unit/integration tests to verify GC settings

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.