openshift/image-registry

OpenShift cluster image registry

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 8 minutes ago
Added to GitGenius on June 23rd, 2023
Created on October 31st, 2017
Open Issues & Pull Requests: 10 (+0)
GitHub issues: Enabled
Number of forks: 100
Total Stargazers: 51 (+0)
Total Subscribers: 149 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 34.8 hours
Mean response time: 31.7 days
90th percentile: 93.7 days
Tracked items: 3

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 88 days
Stale 30+ days: 1
Stale 90+ days: 0

Recent activity

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

Top labels

  • lifecycle/rotten (4)
  • area/tests (3)
  • kind/bug (3)
  • priority/P2 (3)
  • tide/merge-blocker (3)
  • priority/P1 (2)
  • kind/documentation (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

OpenShift Image Registry is a container image registry tightly integrated with OpenShift Origin that enables distribution of Docker images within Kubernetes clusters.

The tool solves the problem of managing and distributing container images in OpenShift environments. It provides image pull and caching capabilities from remote registries, allowing clusters to store and serve images locally. The registry includes role-based access control to restrict who can push and pull images, audit logging to track registry operations, and Prometheus metrics for monitoring registry performance and health.

Organizations running OpenShift clusters should adopt this tool as their primary image distribution mechanism, since it is purpose-built for that platform rather than a generic registry. It suits projects that need tight integration with OpenShift's authentication and authorization systems, as well as those requiring audit trails and observability of image operations. The README does not compare it to alternative registries.

Work in the issue tracker is dominated by merge-blocker labels, indicating that the project prioritizes resolving blocking issues before accepting new changes.