Notable features in odo 1.0

odo 1.0 offers a simple way to develop applications on OpenShift Container Platform. odo is completely client-based and requires no server within OpenShift Container Platform cluster.

odo 1.0 comes with:

  • Simple syntax and design centered around concepts familiar to developers such as projects, applications and components.

  • Compatibility with any language or runtime within the OpenShift catalog of component types.

  • Capability to add custom component types using custom image builders.

  • Official support for Java and Node.js component types.

  • Service catalog which allows users to connect applications deployed on OpenShift Container Platform cluster to the Template Service Broker.

  • odo service create - an interactive mode which guides users through the process of creating applications.

  • odo watch - a feature that automatically detects changes to local code and applies the changes to the component in real time.

Getting support


If you have found an error or have suggestions for improving the documentation, file an issue in Bugzilla. Choose the OpenShift Container Platform product type and the Documentation component type.


If you have found an error, encountered a bug or have suggestions for improving the functionality of odo, file an issue in Bugzilla. Choose the OpenShift Container Platform product type and the odo component type.

Provide as many details in the description of the issue as possible.

Technology Preview features in odo 1.0

Technology Preview features are not fully supported, may not be functionally complete, and are not suitable for deployment in production. Customers are encouraged to provide feedback and functionality suggestions for a Technology Preview feature before it becomes fully supported.

  • odo debug is a feature that allows users to attach a local debugger to a component running in the Pod on OpenShift Container Platform.

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

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

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

Known issues

  • Bug 1760573 An active pointer is not pointing to a current active project.

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

  • Bug 1760575 odo app delete removes application components but not services.

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

  • Bug 1760580 catalog list components does not list out components of a specified namespace.

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

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

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

  • Bug 1760587 odo reports an invalid flag when a non-existent command is used.

  • Bug 1760588 odo service create crashes when run in Cygwin.

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

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

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

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

  • Bug 1761443 Deleted files are not removed from a Java component.