Okteto Registry

The Okteto Registry allows every Okteto Namespace to have its own space to store its container images.

Push container images to the Okteto Registry

The recommended way to use the Okteto Registry is by installing and configuring the Okteto CLI.

The Okteto CLI is automatically configured to interact with the Okteto Registry. For example, if your have the following Okteto Manifest:

okteto.yml

build:
  api:
    context: api
  frontend:
    context: frontend

The command okteto build will build and automatically push the api and frontend images to the Okteto Registry:

okteto build

 i  Using cindy @ okteto.example.com as context
 i  Building 'api/Dockerfile' in tcp://buildkit.okteto.example.com:443...
 ...
 ✓  Image 'registry.okteto.example.com/cindy/movies-with-helm-api:okteto' successfully pushed
 i  Building 'frontend/Dockerfile' in tcp://buildkit.okteto.example.com:443...
 ...
 ✓  Image 'registry.okteto.example.com/cindy/movies-with-helm-frontend:okteto' successfully pushed

The final image name depends on the Okteto Registry URL, your current namespace, the name of your git repository and the name of your image in the Okteto Manifest. But you don't need to remember the image names, you should access them using the following environment variables:

• api: OKTETO_BUILD_API_IMAGE
• frontend: OKTETO_BUILD_FRONTEND_IMAGE

Read more about the available environment variables to access your images here.

Pull container images from the Okteto Registry

Any image pushed into the Okteto Registry is private. You'll need to authenticate with the registry before pulling an image.

Namespaces in Okteto are automatically allowed to pull images that belong to their namespace automatically. If your application uses images from the Okteto Registry, it'll be able to pull container images without any extra configuration.

Push Helm chart to the Okteto Registry

You can push Helm charts to the Okteto Registry, but this process isn't integrated with the Okteto CLI. The first step is to log in to the Okteto Registry where you want to push the Helm chart. For this you will need some credentials that you can obtain by executing the okteto context show --include-token command. This command will show you information about the current okteto context in use:

{
    "name": "https://okteto.example.com",
    "id": "3cf4529c-1gbd-4364-99cf-3f4bbe499adb",
    "username": "cindy",
    "token": "i3kDEh4FKqrJzY7e7Qamd8CfTTrjkPOTN5ftHoKl",
    "namespace": "cindy",
    "builder": "tcp://buildkit.okteto.example.com:1234",
    "registry": "registry.okteto.example.com",
    "personalNamespace": "cindy",
    "isOkteto": true
}

You can retrieve your username, password (token), and the domain for your registry from the output. You can also use the environment variables OKTETO_USERNAME, OKTETO_TOKEN, OKTETO_NAMESPACE and OKTETO_REGISTRY if your script is running as part of the deploycommands of your Okteto Manifest. For example:

okteto.yml

deploy:
  - helm registry login ${OKTETO_REGISTRY} -u ${OKTETO_USERNAME} -p ${OKTETO_TOKEN}

Once you are logged in you will need to package the chart.

okteto.yml

deploy:
  - helm package ./chart

After that you can push the packaged Helm chart to the registry.

okteto.yml

deploy:
  - helm push ./movies-api-0.1.0.tgz oci://${OKTETO_REGISTRY}/${OKTETO_NAMESPACE}

Pull Helm chart to the Okteto Registry

Once the packaged chart has been pushed to the Okteto Registry, you can pull it by using the command below:

okteto.yml

deploy:
  - helm registry login ${OKTETO_REGISTRY} -u ${OKTETO_USERNAME} -p ${OKTETO_TOKEN}
  - helm pull oci://${OKTETO_REGISTRY}/${OKTETO_NAMESPACE}/movies-api --version 0.1.0