mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-06 15:46:57 +01:00
110 lines
4.9 KiB
Plaintext
110 lines
4.9 KiB
Plaintext
[id='odo-release-notes']
|
|
= `{odo-title}` release notes
|
|
include::modules/developer-cli-odo-attributes.adoc[]
|
|
include::modules/common-attributes.adoc[]
|
|
:context: odo-release-notes
|
|
toc::[]
|
|
|
|
[id="odo-notable-improvements_{context}"]
|
|
== Notable changes and improvements in `{odo-title}`
|
|
|
|
* 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-title}` now supports Ingress to create URLs on Kubernetes.
|
|
|
|
|
|
[id="odo-getting-support_{context}"]
|
|
== Getting support
|
|
|
|
.For Documentation
|
|
|
|
If you find an error or have suggestions for improving the documentation, file an issue in link:http://bugzilla.redhat.com[Bugzilla]. Choose the *{product-title}* 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-title}`, file an issue in link:http://bugzilla.redhat.com[Bugzilla]. Choose the *Red Hat {odo-title} for {product-title}* product type.
|
|
|
|
Provide as many details in the issue description as possible.
|
|
|
|
[id="odo-fixed-issues_{context}"]
|
|
== Fixed issues
|
|
|
|
* link:https://bugzilla.redhat.com/show_bug.cgi?id=1760575[Bug 1760575] The `odo app delete` command removes application components but not Services.
|
|
|
|
* link:https://bugzilla.redhat.com/show_bug.cgi?id=1760577[Bug 1760577] The `odo push` command does not delete the OpenShift objects when the component name is changed.
|
|
|
|
|
|
[id="odo-known-issues_{context}"]
|
|
== Known issues
|
|
|
|
* link:https://bugzilla.redhat.com/show_bug.cgi?id=1760574[Bug 1760574] A deleted namespace is listed in the `odo project get` command.
|
|
|
|
* link:https://bugzilla.redhat.com/show_bug.cgi?id=1760586[Bug 1760586] The `odo delete` command starts an infinite loop after a project is deleted and a component name is set.
|
|
|
|
* link:https://bugzilla.redhat.com/show_bug.cgi?id=1760588[Bug 1760588] The `odo service create` command crashes when run in Cygwin.
|
|
|
|
* link:https://bugzilla.redhat.com/show_bug.cgi?id=1760590[Bug 1760590] In Git BASH for Windows, the `odo login -u developer` command does not hide a typed password when requested.
|
|
|
|
* link:https://bugzilla.redhat.com/show_bug.cgi?id=1783188[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.
|
|
|
|
* link:https://bugzilla.redhat.com/show_bug.cgi?id=1761440[Bug 1761440] It is not possible to create two Services of the same type in one project.
|
|
|
|
* link:https://bugzilla.redhat.com/show_bug.cgi?id=1821643[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>
|
|
----
|
|
|
|
[id="odo-technology-preview_{context}"]
|
|
== Technology Preview features `{odo-title}`
|
|
|
|
* `odo debug` is a feature that allows users to attach a local debugger to a component running in the Pod. To learn more, see xref:../../cli_reference/developer_cli_odo/debugging-applications-in-odo.adoc#debugging-an-application_debugging-applications-in-odo[Debugging applications in odo]
|
|
|
|
:FeatureName: odo debug
|
|
include::modules/technology-preview.adoc[leveloffset=+1]
|
|
|
|
* Devfile support. You can now create and deploy your applications using the devfiles with `{odo-title}`. 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`
|
|
|
|
:FeatureName: Devfile support
|
|
include::modules/technology-preview.adoc[leveloffset=+1]
|