This is a cache of https://docs.openshift.com/container-platform/4.4/cli_reference/developer_cli_odo/odo-release-notes.html. It is a snapshot of the page at 2024-11-05T01:20:59.701+0000.
odo release notes - Developer CLI (odo) | CLI tools | OpenShift Container Platform 4.4
  1. Documentation
    2. history
×

odo release notes

Notable changes and improvements in odo

  • A --now flag is added for odo create, odo url, and odo config.

    Run odo url create --now to create the URL in the configuration and propagate all the changes to the cluster.

  • An odo debug info command is added. The command displays if the debug mode is enabled for a component, if the port-forward process is running, and information about ports used.

  • The odo push output now shows the exact error from the OpenShift cluster on failure.

  • A --secure flag is added for odo url. It indicates whether a URL is secure.

  • odo storage list now displays the information about the storage state: Pushed, NotPushed or Locally Deleted.

  • odo debug port-forward now selects a port automatically if the default port (5858) is occupied.

  • The --all flag is renamed to --all-apps.

  • The default PVC size has been increased to 10GiB.

  • The JSON output for odo storage list -o json has been restructured.

  • nodejs-8 and nodejs-10 images are no longer supported.

  • Experimental mode feature. By default, features under development or in experimental mode are hidden from the user.

    • To enable experimental mode, run:

      $ odo config set --env ODO_EXPERIMENTAL=true

      or

      $ odo preference set experimental true

    • To disable experimental mode, run:

      $ odo config unset --env ODO_EXPERIMENTAL

      or

      $ odo preference set experimental false

  • odo now supports Ingress to create URLs on Kubernetes.

Getting support

For Documentation

If you find 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.

For Product

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

Provide as many details in the issue description as possible.

Fixed issues

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

Known issues

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

    Workaround: specify your .NET project file by running:

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

Technology Preview features odo

  • 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

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

  • Devfile support. You can now create and deploy your applications using the devfiles with odo. A devfile is a file that defines the development environment: environment variables, image, and so on. To access this feature, you must enable experimental mode with odo preference set experimental true.

    To see the list of currently supported devfile components, run odo catalog list components

Devfile support 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/.