This documentation is for a release that is no longer maintained
See documentation for the latest supported version 3 or the latest supported version 4.2.15. odo release notes
2.15.1. Notable changes and improvements in odo 复制链接链接已复制到粘贴板!
-
The
--devfile
flag is added toodo create
. Runodo 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:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
The
--starter
flag is added toodo create
. Runodo 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 toodo push
. With--context
, you can triggerodo push
from outside the source code directory. Runodo 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 forodo 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
. Runodo push -o json
to display event notifications in JSON format.
2.15.2. 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.
2.15.3. 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>
$ odo config set --env DOTNET_STARTUP_PROJECT=<path to your project file>
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
2.15.4. 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. 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
.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/.
-
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 withodo preference set experimental true
.
Operators 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/.