mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
odo release notes
This commit is contained in:
Yana Hontyk
committed by
openshift-cherrypick-robot
openshift-cherrypick-robot
parent
0f17ad6096
commit
265eeaf266
@@ -5,9 +5,6 @@ include::modules/common-attributes.adoc[]
|
||||
:context: creating-instances-of-services-managed-by-operators
|
||||
toc::[]
|
||||
|
||||
:FeatureName: Creating instances of services managed by Operators in `{odo-title}`
|
||||
include::modules/technology-preview.adoc[leveloffset=+1]
|
||||
|
||||
Operators are a method of packaging, deploying, and managing Kubernetes services. With `{odo-title}`, you can create instances of services from the Custom Resource Definitions (CRDs) provided by the Operators. You can then use these instances in your projects and link them to your components.
|
||||
|
||||
To create services from an Operator, you must ensure that the Operator has valid values defined in its `metadata` to start the requested service. `{odo-title}` uses the `metadata.annotations.alm-examples` YAML file of an Operator to start
|
||||
@@ -17,8 +14,6 @@ the service. If this YAML has placeholder values or sample values, a service can
|
||||
* Install the `oc` CLI and log into the cluster.
|
||||
** Note that the configuration of the cluster determines the services available to you. To access the Operator services, a cluster administrator must install the respective Operator on the cluster first. To learn more, see xref:../../operators/admin/olm-adding-operators-to-cluster.adoc#olm-installing-operators-from-operatorhub_olm-adding-operators-to-a-cluster[Adding Operators to the cluster].
|
||||
* Install the `{odo-title}` CLI.
|
||||
* Enable experimental mode. To enable experimental mode in `{odo-title}`, run:
|
||||
`odo preference set Experimental true` or use the environment variable `odo config set --env ODO_EXPERIMENTAL=true`
|
||||
|
||||
include::modules/developer-cli-odo-creating-a-project-in-odo.adoc[leveloffset=+1]
|
||||
include::modules/developer-cli-odo-listing-available-services-from-the-operators-installed-on-the-cluster.adoc[leveloffset=+1]
|
||||
|
||||
@@ -8,48 +8,22 @@ toc::[]
|
||||
[id="odo-notable-improvements_{context}"]
|
||||
== Notable changes and improvements in `{odo-title}`
|
||||
|
||||
* The `--devfile` flag is added to `odo create`. Run `odo create <component name> --devfile <devfile path>` to specify your devfile location. This flag is only available in the Experimental Mode. See xref:odo-technology-preview_odo-release-notes[Technology Preview features] to learn how to enable it.
|
||||
* `{odo-title}` integration with devfiles is no longer a Technology Preview feature and is now fully supported. To learn more, see xref:../../cli_reference/developer_cli_odo/using-devfiles-in-odo.adoc#creating-a-java-application-by-using-a-devfile[Creating applications by using devfiles].
|
||||
|
||||
* Dynamic registry support. Now you can configure your own registries with the following commands:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
# Add a registry to the registry list
|
||||
odo registry add <registry name> <registry URL>
|
||||
* The default deployment mechanism in `{odo-title}` is the devfile deployment now.
|
||||
|
||||
# List a registry in the registry list
|
||||
odo registry list
|
||||
* Added documentation about converting S2I to devfile. See, xref:../../cli_reference/developer_cli_odo/using-devfiles-in-odo.adoc#converting-an-s2i-component-into-a-devfile-component_creating-applications-by-using-devfiles[Converting an S2I component into a devfile component].
|
||||
|
||||
# Delete a registry from the registry list
|
||||
odo registry delete <registry name>
|
||||
* Added commands to display JSON output for devfile components.
|
||||
|
||||
# Update a registry in the registry list
|
||||
odo registry update <registry name> <registry URL>
|
||||
* `odo debug` is no longer a Technology Preview feature and is now fully supported.
|
||||
To learn more, see xref:../../cli_reference/developer_cli_odo/debugging-applications-in-odo.html#debugging-an-application_debugging-applications-in-odo[Debugging applications in odo].
|
||||
|
||||
# List a component with a corresponding registry
|
||||
odo catalog list components
|
||||
* `{odo-title}` integration with Operators is no longer a Technology Preview feature and is now fully supported. To learn more, see xref:../../cli_reference/developer_cli_odo/creating-instances-of-services-managed-by-operators.adoc[Creating instances of services managed by Operators].
|
||||
|
||||
# Create a component that is hosted by a specific registry
|
||||
odo create <component type> --registry <registry name>
|
||||
----
|
||||
|
||||
* The `--starter` flag is added to `odo create`. Run `odo 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 to `odo push`. With `--context`, you can trigger `odo push` from outside the source code directory. Run `odo 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 for `odo 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`. Run `odo push -o json` to display event notifications in JSON format.
|
||||
* `{odo-title}` now supports IBM Z.
|
||||
|
||||
* Improved and enhanced output for many commands.
|
||||
|
||||
[id="odo-getting-support_{context}"]
|
||||
== Getting support
|
||||
@@ -93,23 +67,5 @@ 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.html#debugging-an-application_debugging-applications-in-odo[Debugging applications in odo].
|
||||
|
||||
:FeatureName: odo debug
|
||||
include::modules/technology-preview.adoc[leveloffset=+1]
|
||||
|
||||
* Devfile support. With {odo-title}, you can create and deploy your applications using the devfiles. To learn more, see xref:../../cli_reference/developer_cli_odo/using-devfiles-in-odo.adoc#creating-a-java-application-by-using-a-devfile[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`.
|
||||
|
||||
:FeatureName: Devfile support
|
||||
include::modules/technology-preview.adoc[leveloffset=+1]
|
||||
|
||||
* Operators support. You can now create services from Operators with `{odo-title}`. To learn more, see xref:../../cli_reference/developer_cli_odo/creating-instances-of-services-managed-by-operators.adoc[Creating instances of services managed by Operators]. To access this feature, you must enable Experimental Mode with `odo preference set experimental true`.
|
||||
|
||||
:FeatureName: Operators support
|
||||
include::modules/technology-preview.adoc[leveloffset=+1]
|
||||
//[id="odo-technology-preview_{context}"]
|
||||
//== Technology Preview features `{odo-title}`
|
||||
|
||||
@@ -5,9 +5,6 @@ include::modules/common-attributes.adoc[]
|
||||
:context: creating-applications-by-using-devfiles
|
||||
toc::[]
|
||||
|
||||
:FeatureName: Creating applications by using devfiles with `{odo-title}`
|
||||
include::modules/technology-preview.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/developer-cli-odo-about-devfiles-in-odo.adoc[leveloffset=+1]
|
||||
|
||||
== Creating a Java application by using a devfile
|
||||
@@ -16,8 +13,6 @@ include::modules/developer-cli-odo-about-devfiles-in-odo.adoc[leveloffset=+1]
|
||||
|
||||
* You have installed `{odo-title}`.
|
||||
* You must know your ingress domain cluster name. Contact your cluster administrator if you do not know it. For example, `apps-crc.testing` is the cluster domain name for https://access.redhat.com/documentation/en-us/red_hat_codeready_containers/[Red Hat CodeReady Containers].
|
||||
* You have enabled Experimental Mode in `{odo-title}`.
|
||||
** To enable Experimental Mode in `{odo-title}` preferences, run `odo preference set Experimental true` or use the environment variable `odo config set --env ODO_EXPERIMENTAL=true`
|
||||
|
||||
include::modules/developer-cli-odo-creating-a-project-in-odo.adoc[leveloffset=+2]
|
||||
|
||||
|
||||
Reference in New Issue
Block a user