HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
kubernetes
registry.k8s.io
Go2023–2023
kubernetes / registry.k8s.io

registry.k8s.io

This project is the repo for registry.k8s.io, the production OCI registry service for Kubernetes' container image artifacts

2Distinct people
3Mentions
0Explicit recommenders
537GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

This project is the repo for registry.k8s.io, the production OCI registry service for Kubernetes' container image artifacts

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 2:19:09 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval3 dated mentions

Observed mentions: 2023-03-15 20:40:18 UTC to 2023-03-18 08:18:01 UTC.

012023-03-15 18:00:00 UTC to 2023-03-15 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 15, 18:002023-03-15 21:00:00 UTC to 2023-03-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-16 00:00:00 UTC to 2023-03-16 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-16 03:00:00 UTC to 2023-03-16 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-16 06:00:00 UTC to 2023-03-16 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-16 09:00:00 UTC to 2023-03-16 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-16 12:00:00 UTC to 2023-03-16 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-16 15:00:00 UTC to 2023-03-16 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-16 18:00:00 UTC to 2023-03-16 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-16 21:00:00 UTC to 2023-03-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-17 00:00:00 UTC to 2023-03-17 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 17, 00:002023-03-17 03:00:00 UTC to 2023-03-17 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-17 06:00:00 UTC to 2023-03-17 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-17 09:00:00 UTC to 2023-03-17 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-17 12:00:00 UTC to 2023-03-17 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-17 15:00:00 UTC to 2023-03-17 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-17 18:00:00 UTC to 2023-03-17 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-17 21:00:00 UTC to 2023-03-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-18 00:00:00 UTC to 2023-03-18 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-18 03:00:00 UTC to 2023-03-18 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-03-18 06:00:00 UTC to 2023-03-18 09:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 18, 06:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 15, 18:002023-03-15 18:00:00 UTC2023-03-15 21:00:00 UTC101
Mar 15, 21:002023-03-15 21:00:00 UTC2023-03-16 00:00:00 UTC000
Mar 16, 00:002023-03-16 00:00:00 UTC2023-03-16 03:00:00 UTC000
Mar 16, 03:002023-03-16 03:00:00 UTC2023-03-16 06:00:00 UTC000
Mar 16, 06:002023-03-16 06:00:00 UTC2023-03-16 09:00:00 UTC000
Mar 16, 09:002023-03-16 09:00:00 UTC2023-03-16 12:00:00 UTC000
Mar 16, 12:002023-03-16 12:00:00 UTC2023-03-16 15:00:00 UTC000
Mar 16, 15:002023-03-16 15:00:00 UTC2023-03-16 18:00:00 UTC000
Mar 16, 18:002023-03-16 18:00:00 UTC2023-03-16 21:00:00 UTC000
Mar 16, 21:002023-03-16 21:00:00 UTC2023-03-17 00:00:00 UTC000
Mar 17, 00:002023-03-17 00:00:00 UTC2023-03-17 03:00:00 UTC000
Mar 17, 03:002023-03-17 03:00:00 UTC2023-03-17 06:00:00 UTC000
Mar 17, 06:002023-03-17 06:00:00 UTC2023-03-17 09:00:00 UTC000
Mar 17, 09:002023-03-17 09:00:00 UTC2023-03-17 12:00:00 UTC000
Mar 17, 12:002023-03-17 12:00:00 UTC2023-03-17 15:00:00 UTC000
Mar 17, 15:002023-03-17 15:00:00 UTC2023-03-17 18:00:00 UTC000
Mar 17, 18:002023-03-17 18:00:00 UTC2023-03-17 21:00:00 UTC000
Mar 17, 21:002023-03-17 21:00:00 UTC2023-03-18 00:00:00 UTC000
Mar 18, 00:002023-03-18 00:00:00 UTC2023-03-18 03:00:00 UTC000
Mar 18, 03:002023-03-18 03:00:00 UTC2023-03-18 06:00:00 UTC101
Mar 18, 06:002023-03-18 06:00:00 UTC2023-03-18 09:00:00 UTC101

What Hacker News says

1 sources
One annoyance with how docker images are specified is they include the location where they are stored. So if you want to change where you store you image you break everyone. I wonder if what regsitry.k8s.io does could be generalized: https://github.com/kubernetes/registry.k8s.io/blob/main/cmd/... The idea is the depending on which cloud you are pulling the image from, they will use the closest blob store to service the request. This also has the effect that you could change the source of truth for the registry without breaking all Dockerfiles.
In Docker is deleting Open Source organisations - what you need to know

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.