Azure / Azure/peerd

Peerd Capability for Preemptive Pulling of OCI Content

Open
#66 0 comments 1 reaction 0 assignees View on GitHub
enhancement
Dominant language
Go
Stars
134
Forks
23
PR merge metrics
No merged PRs in 30d

Description

From docs, customers that want to pull large OCI format images (think large LLM images with gigabyte weights) to a multi-thousand node K8S cluster have no intuitive way to "warm" up workload scale up. A K8S admin interested in this scenario can of course create 1 pod, pull the image to that pod (which causes the workload to begin executing on that pod), before scaling to more pods to leverage P2P.

However, a customer may be interested in pre-emptively caching OCI content on the cluster (1) without image pulls and (2) without the pulled image running on any pod because they are interested in all images running at the same time. This isn't easily done and requires a lot of manual K8S scripts to achieve.

If Peerd had an intuitive CLI command or a K8S YAML experience for "pre-warming", it would facilitate community adoption.

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.