Notable improvements in odo 1.1.0

  • IBM Z and PowerPC architecture binaries are now available.

  • odo catalog has been improved to provide more useful output information.

  • Information prompts have been added to the odo service create command, providing possible next step scenarios.

  • Log verbosity can now be set with an environment variable ODO_LOG_LEVEL.

  • Use odo preference set PushTimeout <seconds> to specify the number of seconds odo waits for a component Pod to be deployed before the command fails.

  • Overall documentation improvements. The documentation now includes a description of `odo’s inner architecture.

Getting support

For Documentation

If you find an error or have suggestions for improving the documentation, file an issue in Bugzilla. Choose the Azure Red Hat OpenShift product type and the Documentation component type.

For Product

If you find an error, encountered a bug, or have suggestions for improving the functionality of odo, file an issue in Bugzilla. Choose the Red Hat odo for Azure Red Hat OpenShift product type.

Provide as many details in the issue description as possible.

Fixed issues

  • Bug 1760573 The active pointer does not switch to the current active project after the deletion of a project.

  • Bug 1760578 The odo watch command does not fail with an error message for Git-based components, but it should.

  • Bug 1760583 The odo config unset command does not unset an environment variable, but says it did.

  • Bug 1760585 The odo delete --all command deletes the $HOME/.odo folder when run from $HOME.

  • Bug 1760589 Autocompletion does not work for the --context flag in odo push.

  • Bug 1761442 The component create command fails when used with the --context flag and --binary flag if the binary is located in a temporary folder.

  • Bug 1783179 When you set an environment variable, create a URL route, and then change the source code of the component, the URL route becomes inaccessible.

Known issues

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

  • Bug 1760575 The odo app delete command removes application components but not Services.

  • Bug 1760577 The odo push command does not delete the OpenShift objects when the component name is changed.

  • 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.

Technology Preview features in odo 1.1.0

odo debug is a feature that allows users to attach a local debugger to a component running in the Pod on Azure Red Hat OpenShift.

odo debug is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/.

  • Use the odo debug port-forward command to start port forwarding.

  • Use the odo config set DebugPort 9292 command to specify the remote port that the debugging agent should run on.

  • Use the odo debug port-forward --local-port 9292 command to specify the local port for port forwarding.