First, export the VERSION
and CUSTOM-DOCKER-REGISTRY
environment variables in your shell:
Replace <YOUR-DESIRED-VERSION>
with the version of the Odigos images you want to use, <YOUR-CUSTOM-DOCKER-REGISTRY>
with the URL of your custom Docker registry, and <YOUR-PLATFORM-ARCHITECTURE>
with the platform architecture of the environment where you are deploying Odigos (linux/amd64, linux/arm64).
Start by pulling the required images from the official Odigos registry onto your local machine or CI environment:
Odigos component images are published in multi-arch for ARM64 and AMD64 architectures. When pulling these images, be sure to specify the correct architecture for the environment they will be deployed.
Next, Tag each image with your custom Docker registry prefix:
Note: Prior to v1.0.155, Odigos images were prefixed with
keyval/
(such askeyval/odigos-scheduler
) In v1.0.155+, this is no longer the case, and Odigos does not assume this prefix. If you were hosting custom images prior to this version, you may have to re-tag your images to remove thekeyval/
prefix.
Now, push the tagged images to your custom Docker registry:
Start by pulling the required images from the official Odigos registry onto your local machine or CI environment:
Odigos component images are published in multi-arch for ARM64 and AMD64 architectures. When pulling these images, be sure to specify the correct architecture for the environment they will be deployed.
Next, Tag each image with your custom Docker registry prefix:
Note: Prior to v1.0.155, Odigos images were prefixed with
keyval/
(such askeyval/odigos-scheduler
) In v1.0.155+, this is no longer the case, and Odigos does not assume this prefix. If you were hosting custom images prior to this version, you may have to re-tag your images to remove thekeyval/
prefix.
Now, push the tagged images to your custom Docker registry:
Start by pulling the required images from the official Odigos registry onto your local machine or CI environment:
Odigos component images are published in multi-arch for ARM64 and AMD64 architectures. When pulling these images, be sure to specify the correct architecture for the environment they will be deployed.
Next, Tag each image with your custom Docker registry prefix:
Note: Prior to v1.0.155, Odigos images were prefixed with
keyval/
(such askeyval/odigos-scheduler
) In v1.0.155+, this is no longer the case, and Odigos does not assume this prefix. If you were hosting custom images prior to this version, you may have to re-tag your images to remove thekeyval/
prefix.
Now, push the tagged images to your custom Docker registry:
If your Docker registry is private, configure your Kubernetes cluster to pull images from it. Refer to the official Kubernetes documentation for guidance: Pull an Image from a Private Registry.
Note: To ensure your Odigos deployments and daemonsets can pull images from a private registry, patch them to add the image pull secret.
Use the following commands:
Finally, install Odigos using the images from your custom Docker registry:
First, export the VERSION
and CUSTOM-DOCKER-REGISTRY
environment variables in your shell:
Replace <YOUR-DESIRED-VERSION>
with the version of the Odigos images you want to use, <YOUR-CUSTOM-DOCKER-REGISTRY>
with the URL of your custom Docker registry, and <YOUR-PLATFORM-ARCHITECTURE>
with the platform architecture of the environment where you are deploying Odigos (linux/amd64, linux/arm64).
Start by pulling the required images from the official Odigos registry onto your local machine or CI environment:
Odigos component images are published in multi-arch for ARM64 and AMD64 architectures. When pulling these images, be sure to specify the correct architecture for the environment they will be deployed.
Next, Tag each image with your custom Docker registry prefix:
Note: Prior to v1.0.155, Odigos images were prefixed with
keyval/
(such askeyval/odigos-scheduler
) In v1.0.155+, this is no longer the case, and Odigos does not assume this prefix. If you were hosting custom images prior to this version, you may have to re-tag your images to remove thekeyval/
prefix.
Now, push the tagged images to your custom Docker registry:
Start by pulling the required images from the official Odigos registry onto your local machine or CI environment:
Odigos component images are published in multi-arch for ARM64 and AMD64 architectures. When pulling these images, be sure to specify the correct architecture for the environment they will be deployed.
Next, Tag each image with your custom Docker registry prefix:
Note: Prior to v1.0.155, Odigos images were prefixed with
keyval/
(such askeyval/odigos-scheduler
) In v1.0.155+, this is no longer the case, and Odigos does not assume this prefix. If you were hosting custom images prior to this version, you may have to re-tag your images to remove thekeyval/
prefix.
Now, push the tagged images to your custom Docker registry:
Start by pulling the required images from the official Odigos registry onto your local machine or CI environment:
Odigos component images are published in multi-arch for ARM64 and AMD64 architectures. When pulling these images, be sure to specify the correct architecture for the environment they will be deployed.
Next, Tag each image with your custom Docker registry prefix:
Note: Prior to v1.0.155, Odigos images were prefixed with
keyval/
(such askeyval/odigos-scheduler
) In v1.0.155+, this is no longer the case, and Odigos does not assume this prefix. If you were hosting custom images prior to this version, you may have to re-tag your images to remove thekeyval/
prefix.
Now, push the tagged images to your custom Docker registry:
If your Docker registry is private, configure your Kubernetes cluster to pull images from it. Refer to the official Kubernetes documentation for guidance: Pull an Image from a Private Registry.
Note: To ensure your Odigos deployments and daemonsets can pull images from a private registry, patch them to add the image pull secret.
Use the following commands:
Finally, install Odigos using the images from your custom Docker registry: