spegel-org/spegel

Stateless cluster local OCI registry mirror.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 33 seconds ago
Added to GitGenius on September 18th, 2026
Created on January 24th, 2023
Open Issues & Pull Requests: 19 (+0)
GitHub issues: Enabled
Number of forks: 168
Total Stargazers: 3,783 (+0)
Total Subscribers: 21 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 33.1 hours
Mean response time: 44.5 days
90th percentile: 80.9 days
Tracked items: 162

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 11% of issues opened in the past year have never received a reply. 98% of issues opened in the past year have since been closed. Three people close 88% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 8
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 813 days
Stale 30+ days: 6
Stale 90+ days: 4

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (50)
  • help wanted (8)

Detailed Description

Spegel is a stateless cluster local OCI registry mirror that caches container images within a Kubernetes cluster without requiring explicit configuration.

The tool solves the problem of external registry unavailability, rate limiting, and slow image pulls by automatically mirroring OCI images to a local cache accessible to all nodes in the cluster. It operates statelessly, meaning it does not require persistent storage or complex setup, and uses peer-to-peer distribution to share cached images across cluster nodes. When a pod requests an image, Spegel intercepts the request and serves it from the local cache if available, falling back to external registries only when necessary.

Spegel is designed for home lab environments and individual contributor use cases rather than large-scale production deployments. It suits clusters that experience external registry downtime, face Docker Hub rate limits, or operate in edge environments where network efficiency matters. The project explicitly notes that it has an evolving API with no guaranteed support, and assistance is provided on a best-effort basis.

The project maintains a measured development pace with selective engagement on issues and pull requests. Releases occur at intervals, and the maintainers prioritize stability and core functionality over rapid feature expansion. The codebase remains focused on the stated use cases rather than attempting to serve all possible registry mirroring scenarios.