odo release notes

    • odo create -s2i now converts an S2I component into a devfile component. When running odo create --s2i <component-type> odo now creates a converted Devfile component based on the S2I images of the specified component type.

      Note that this feature introduces many breaking changes, see Known Issues to learn more.

    • Operator based service is now created on the cluster only after you run odo push and not after odo service create anymore.

    • You can now use the --container flag to specify the container you want to attach storage to when running command. See to learn the details.

    • Commands that implement changes directly on a cluster now display a message informing a user that odo push is not required.

    • When creating a component from a devfile, odo create now uses a default component name if the name is not specified.

    • odo now has Telemetry. See Telemetry section to learn how to modify your Telemetry consent preferences.

    For Documentation

    If you find an error or have suggestions for improving the documentation, file an issue in . Choose the OKD 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 OpenShift Developer Tools and Services as a product type and odo as a component.

    Provide as many details in the issue description as possible.

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

    • The odo service create command crashes when run in Cygwin.

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

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

    • When running odo url create after odo create --s2i, the command fails. odo creates a URL now directly without asking.

    • Wildfly and dotnet S2I components cannot be created with odo create.

    • odo env set DebugPort does not work with converted devfile components. Workaround: use odo config set --env DEBUG_PORT.

    • odo delete --wait does not wait for the resources to be terminated for devfile components.