odo uses different catalogs to deploy components and services.
odo uses the portable devfile format to describe the components. It can connect to various devfile registries to download devfiles for different languages and frameworks. See
odo registry for more information.
You can list all the devfiles available on the different registries with the command:
You can get more information about a specific component with the command:
Registry is the registry from which the devfile is retrieved.
Starter projects are sample projects in the same language and framework of the devfile, that can help you start a new project. See
odo create for more information on creating a project from a starter project.
odo can deploy services with the help of operators.
You can get the list of available operators and their associated services with the command:
In this example, you can see that two operators are installed in the cluster. The
postgresql-operator.v0.1.1 operator can deploy services related to PostgreSQL:
redis-operator.v0.8.0 operator can deploy services related to Redis:
Note: To get a list of all the available operators, odo fetches the
CSV) resources of the current namespace that are in a Succeeded phase. For operators that support cluster-wide access, when a new namespace is created, these resources are automatically added to it, but it may take some time before they are in the Succeeded phase, and odo may return an empty list until the resources are ready.
You can search for a specific service by a keyword with the command:
You may see a similar list that contains only the relevant operators, whose name contains the searched keyword.
You can get more information about a specific service with the command:
A service is represented in the cluster by a
CustomResourceDefinition (commonly named
CRD). This command will display the details about this CRD such as
version, and the list of fields available to define an instance of this custom resource.
The list of fields is extracted from the OpenAPI schema included in the
CRD. This information is optional in a
CRD, and if it is not present, it is extracted from the
CSV) representing the service instead.
It is also possible to request description of operator backed service without providing crd type information. Let us say you want to describe redis operator on cluster without CRD, you can do