odo release notes

The --devfile flag is added to odo create. Run odo create <component name> --devfile <devfile path> to specify your devfile location. This flag is only available in the Experimental Mode. See Technology Preview features to learn how to enable it.

Dynamic registry support. Now you can configure your own registries with the following commands:

# Add a registry to the registry list
odo registry add <registry name> <registry URL>

# List a registry in the registry list
odo registry list

# Delete a registry from the registry list
odo registry delete <registry name>

# Update a registry in the registry list
odo registry update <registry name> <registry URL>

# List a component with a corresponding registry
odo catalog list components

# Create a component that is hosted by a specific registry
odo create <component type> --registry <registry name>

The --starter flag is added to odo create. Run odo create nodejs --starter <project-name> to download the source code of a project specified in the devfile. If no project name is specified, odo downloads the first one.

The --context flag is added to odo push. With --context, you can trigger odo push from outside the source code directory. Run odo push --devfile <path to the devfile> --context <directory with your component> to specify the directory of your component.

Performance improvement for odo catalog list components when using the devfiles.

The --now flag is added for odo url delete when using the devfiles.

odo url delete --now now works with the devfiles.

The --debug flag now works with the devfiles.

Added machine-readable output for listing Operator-backed services. Run odo catalog list services -o json to display information about Operators and services in JSON format.

Added machine-readable output for debugging. Run odo debug info -o json to display the debugging information in JSON format.

Added machine-readable output for odo push. Run odo push -o json to display event notifications in JSON format.

Bug 1760574 A deleted namespace is listed in the odo project get command.

Bug 1760586 The odo delete command starts an infinite loop after a project is deleted and a component name is set.

Bug 1760588 The odo service create command crashes when run in Cygwin.

Bug 1760590 In Git BASH for Windows, the odo login -u developer command does not hide a typed password when requested.

Bug 1783188 In a disconnected cluster, the odo component create command throws an error …​tag not found…​ despite the component being listed in the catalog list.

Bug 1761440 It is not possible to create two Services of the same type in one project.

Bug 1821643 odo push does not work on the .NET component tag 2.1+.

$ odo config set --env DOTNET_STARTUP_PROJECT=<path to your project file>

odo debug is a feature that allows users to attach a local debugger to a component running in the Pod. To learn more, see Debugging applications in odo.

Devfile support. With odo, you can create and deploy your applications using the devfiles. To learn more, see Creating applications by using devfiles. To access this feature, you must enable Experimental Mode with odo preference set experimental true.

Operators support. You can now create services from Operators with odo. To learn more, see Creating instances of services managed by Operators. To access this feature, you must enable Experimental Mode with odo preference set experimental true.