-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add blog post for registry.odigos.io
- Loading branch information
Showing
1 changed file
with
32 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
--- | ||
pubDate: 'Feb 18 2025' | ||
title: 'Odigos is moving to a new container registry' | ||
image: '/registry_cover.png' | ||
category: 'Odigos' | ||
description: 'Odigos images will now be hosted on regsitry.odigos.io' | ||
tags: [odigos] | ||
authorImage: '/mike.jpg' | ||
author: Mike Dame | ||
metadata: application management | ||
--- | ||
|
||
Odigos images are now available at a new location: `registry.odigos.io`. | ||
|
||
Starting in Odigos v1.0.155, all component images will pull from | ||
`registry.odigos.io` instead of DockerHub. We have decided to migrate | ||
from DockerHub to our own hosted registry to serve our users directly | ||
and without pull limits imposed by DockerHub. | ||
|
||
What this means is that you can now install Odigos without configuring | ||
DockerHub credentials or pull secrets in your cluster. | ||
|
||
In addition, Odigos images will no longer have a `keyval/` prefix. For | ||
example, in v1.0.154 the Odiglet image | ||
`docker.io/keyval/odigos-odiglet:v1.0.154` is now | ||
`registry.odigos.io/odigos-odiglet:v1.0.155`. | ||
|
||
For users that are currently re-hosting images in their own registry | ||
(and installing with a custom `--image-prefix`), please note our new | ||
[instructions for installing Odigos from a custom Docker | ||
registry](https://docs.odigos.io/setup/docker-registry) and ensure | ||
your image tags match the new format. |