Skip to main content
Version: v3

Using Devfile Registries declared in the cluster

Besides getting the list of Devfile Registries to work with from the local configuration file, odo can automatically detect Devfile Registries declared in the current cluster, and use them.

It does so by detecting the presence of the following Custom Resources in the current cluster:

  • ClusterDevfileRegistriesList: installable at the cluster level
  • DevfileRegistriesList: installable at the namespace level

More details on the Devfile Registry Operator documentation.


Registries declared in ClusterDevfileRegistriesList and DevfileRegistriesList Custom Resources do not necessarily need to be deployed and running in the cluster. Only their URLs are listed in those resources.

Registries listed in the Custom Resources above are added automatically to the top of the list of registries usable by odo, and odo will use them in the following priority order:

  1. registries from the current namespace (declared in the DevfileRegistriesList resource)
  2. cluster-wide registries (declared in the ClusterDevfileRegistriesList resource)
  3. all other registries configured in the local configuration file

This behavior applies to all odo commands interacting with Devfile registries, such as:

You can use the odo preference view command at any time to see the registries sorted by priority.

Example output:
$ odo preference view

Devfile registries:
ns-devfile-registry No
ns-devfile-staging Yes
cluster-devfile-registry No
cluster-devfile-staging Yes
cluster-devfile-prod Yes
Staging Yes
DefaultDevfileRegistry Yes

Please refer to this blog post for more details on how to deploy a Devfile Registry into a cluster and use it with odo.