SaaSHub helps you find the best software and product alternatives Learn more →
Registry.k8s.io Alternatives
Similar projects and alternatives to registry.k8s.io
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
containers-roadmap
This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
nerdctl
contaiNERD CTL - Docker-compatible CLI for containerd, with support for Compose, Rootless, eStargz, OCIcrypt, IPFS, ...
-
-
-
-
-
-
-
lmctfy
Discontinued lmctfy is the open source version of Google’s container stack, which provides Linux application containers.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better registry.k8s.io alternative or higher similarity.
registry.k8s.io reviews and mentions
Posts with mentions or reviews of registry.k8s.io.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-04.
-
Pull through cache, like AWS just announced
If you stop to think about, what AWS is selling here, it's quite funny. Most of the infrastructure behind registry.k8s.io is hosted on AWS (and also GCP). So AWS essentially tells you: Don't trust the upstream registry, it might go down, cache it on your own registry, hosted also by us.
- Resilient image cache/mirror
-
Announcing pull through cache for registry.k8s.io in Amazon Elastic Container Registry
For example: if you only allow cluster autoscaler and metrics server from registry.k8s.io you can pull those images through the cache as someone who has create repo IAM privileges. If someone without create repo privileges tries to pull a new image it will fail because they can't create the initial repo.
- How are they doing it?
-
registry.k8s.io down from Paris, France?
https://registry.k8s.io (the root url at /) redirects you to https://github.com/kubernetes/registry.k8s.io where we have an issue tracker.
-
FailedCreatePodSandBox
❗ This container is having trouble accessing https://registry.k8s.io
- registry.k8s.io/README.md at main · kubernetes/registry.k8s.io · GitHub
-
How to own your own Docker Registry address
Hosting a forwarding / redirect server instead of actually hosting images is probably a decent idea.
The K8s proxy is redirecting from only hosting on GCR to community-owned registries - https://kubernetes.io/blog/2023/03/10/image-registry-redirec...
You can view the code here - https://github.com/kubernetes/registry.k8s.io
But because everyone is already pointing at gcr.io (just like many openfaas users point at docker.io/) - they're having to do a huge campaign to announce the new URL - the same would apply with the author's solution here.
I wrote some automation for hosting (not redirects) in arkade with the OSS registry - Get a TLS-enabled Docker registry in 5 minutes - https://blog.alexellis.io/get-a-tls-enabled-docker-registry-...
The registry is also something you can run on a VM if you so wish, and have act as a pull through cache.
Apart from reliability - GitHub's container registry is the current next best option - but we have to ask ourselves, what happens when they start charging or the outages start to last longer or are more frequent than 1-2 times per week as we've seen in Q1 2023.
-
Docker's deleting Open Source images and here's what you need to know
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.
-
k8s.gcr.io Image Registry Will Be Frozen From the 3rd of April 2023
If you are using updated helm charts then most of them have already replaced with registry.k8s.io, for example nginx ingress so not really breaking change.
-
A note from our sponsor - SaaSHub
www.saashub.com | 29 Apr 2024
Stats
Basic registry.k8s.io repo stats
20
346
7.2
3 months ago
kubernetes/registry.k8s.io is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of registry.k8s.io is Go.
Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com