README
¶
Peerd
Peerd enhances Azure Artifact Streaming and containerd image pull performance by enabling peer-to-peer distribution in a Kubernetes cluster. Nodes can share streamable content as well as images with each other, which can result in throughput and latency improvements.
Benefits
| Benefit | Artifact Streaming | Image Pulls | Notes |
|---|---|---|---|
| Increased Throughput | ✅ |
✅ |
Both streaming and image pull latency improves. |
| Reduced Cluster Scale Out Time | ✅ |
✅ |
New nodes stream or pull images from peers that already have that content. |
| Improved Cluster Fault Tolerance | ✅ |
✅ |
Mitigating upstream throttling or unavailability. |
| Reduced Container Registry Egress Costs | ✅ |
✅ |
By sharing content within the cluster, upstream I/O is reduced. |
| More Cluster Firewall Configuration Options | ✅ |
✅ |
Once an image or streamable content is ingested, nodes can share from each other without needing to communicate with the container registry. |
| Ease of Use | ✅ |
✅ |
Peerd is a drop-in solution that requires no changes to existing workflows or tooling, with seamless fallback to the container registry if needed. |
Usage Guide
See the usage guide to get started.
Design and Architecture
Read the design.md document to understand the architecture and design of Peerd.
Contributing
Please read our contribution guide which outlines all of our policies, procedures, and requirements for contributing to this project.
Code of Conduct
Please see CODE_OF_CONDUCT.md for further details.
Acknowledgments
- Thanks to Philip Laine and Simon Gottschlag at Xenit for generously sharing their insights on Spegel with us.
- Thanks to DADI P2P Proxy for demonstrating the integration with Overlaybd.
Directories
Click to show internal directories.
Click to hide internal directories.