Add OLM 1.0 relnote for 4.14 #63605
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -472,6 +472,43 @@ For more information about disabling the Image Registry Operator, see xref:../in | |
| [id="ocp-4-14-olm"] | ||
| === Operator lifecycle | ||
|
|
||
| [id="ocp-4-14-olmv1"] | ||
| ==== {olmv1-first} (Technology Preview) | ||
|
|
||
| Operator Lifecycle Manager (OLM) has been included with {product-title} 4 since its initial release. {product-title} {product-version} introduces components for a next-generation iteration of OLM as a Technology Preview feature, known during this phase as _{olmv1}_. This updated framework evolves many of the concepts that have been part of previous versions of OLM and adds new capabilities. | ||
|
|
||
| During this Technology Preview phase of {olmv1} in {product-title} 4.14, administrators can explore the following features: | ||
|
|
||
| Fully declarative model that supports GitOps workflows:: | ||
| {olmv1} simplifies Operator management through two key APIs: | ||
| + | ||
| -- | ||
| * A new `Operator` API, provided as `operators.operators.operatorframework.io` by the new Operator Controller component, streamlines management of installed Operators by consolidating user-facing APIs into a single object. This empowers administrators and SREs to automate processes and define desired states by using GitOps principles. | ||
| * The `Catalog` API, provided by the new Catalogd component, serves as the foundation for {olmv1}, unpacking catalogs for on-cluster clients so that users can discover installable content, such as Operators and Kubernetes extensions. This provides increased visibility into all available Operator bundle versions, including their details, channels, and update edges. | ||
| -- | ||
| + | ||
| For more information, see _Operator Controller_ and _Catalogd_. | ||
|
Contributor
There was a problem hiding this comment. Did you mean to add xrefs here?
Contributor
Author
There was a problem hiding this comment. Sorry, yea, mentioned above in #63605 (comment). |
||
|
|
||
| Improved control over Operator updates:: | ||
| With improved insight into catalog content, administrators can specify target versions for installation and updates. This grants administrators more control over the target version of Operator updates. For more information, see _Installing an Operator from a catalog_. | ||
|
|
||
| Flexible Operator packaging format:: | ||
| Administrators can use file-based catalogs to install and manage the following types of content: | ||
| + | ||
| -- | ||
| * OLM-based Operators, similar to the existing OLM experience | ||
| * _Plain bundles_, which are static collections of arbitrary Kubernetes manifests | ||
| -- | ||
| + | ||
| In addition, bundle size is no longer constrained by the etcd value size limit. For more information, see _Managing catalogs in {olmv1}_. | ||
|
adellape marked this conversation as resolved.
|
||
|
|
||
| [NOTE] | ||
| ==== | ||
| For {product-title} {product-version}, documented procedures for {olmv1} are CLI-based only. Alternatively, administrators can create and view related objects in the web console by using normal methods, such as the *Import YAML* and *Search* pages. However, the existing *OperatorHub* and *Installed Operators* pages do not yet observe {olmv1} components. | ||
| ==== | ||
|
|
||
| For more information, see _{olmv1-first}_. | ||
|
adellape marked this conversation as resolved.
|
||
|
|
||
| [id="ocp-4-14-osdk"] | ||
| === Operator development | ||
|
|
||
|
|
@@ -786,9 +823,10 @@ In the following tables, features are marked with the following statuses: | |
| * _Removed_ | ||
|
|
||
| [discrete] | ||
| [id="ocp-4-14-operators-dep-rem"] | ||
| === Operator lifecycle and development deprecated and removed features | ||
|
|
||
| .Operator lifecycle and development deprecated and removed tracker | ||
| [cols="4,1,1,1",options="header"] | ||
| |==== | ||
| |Feature |4.12 |4.13 |4.14 | ||
|
|
@@ -1703,35 +1741,36 @@ In the following tables, features are marked with the following statuses: | |
| |==== | ||
|
|
||
| [discrete] | ||
| [id="ocp-4-14-operators-tech-preview"] | ||
| === Operator lifecycle and development Technology Preview features | ||
|
|
||
| .Operator lifecycle and development Technology Preview tracker | ||
| [cols="4,1,1,1",options="header"] | ||
| |==== | ||
| |Feature |4.12 |4.13 |4.14 | ||
|
|
||
| |Operator Lifecycle Manager (OLM) v1 | ||
| |Not Available | ||
| |Not Available | ||
| |Technology Preview | ||
|
|
||
| |RukPak | ||
| |Technology Preview | ||
| |Technology Preview | ||
| |Technology Preview | ||
|
|
||
|
Contributor
Author
There was a problem hiding this comment. Removing "Node Observability Operator" from the "Operator lifecycle and development Technology Preview tracker" because it is a duplicate here and is already represented (and is a better fit) over in the "Scalability and performance Technology Preview features" section. |
||
| |Platform Operators | ||
| |Technology Preview | ||
| |Technology Preview | ||
| |Technology Preview | ||
|
|
||
| |Hybrid Helm Operator | ||
|
There was a problem hiding this comment. I guess the |
||
| |Technology Preview | ||
| |Technology Preview | ||
| |Technology Preview | ||
|
|
||
| |Java-based Operator | ||
|
There was a problem hiding this comment. Actually, the
Contributor
Author
There was a problem hiding this comment. We have this section/table titled as "Operator lifecycle and development Technology Preview features", where "Operator lifecyce" is supposed to suggest "OLM", and "[Operator] development" is supposed to suggest "OSDK". So basically we're treating this table as any features related to the fuller Operator Framework. |
||
| |Technology Preview | ||
| |Technology Preview | ||
| |Technology Preview | ||
|
|
||
|
|
@@ -1792,6 +1831,11 @@ In the following tables, features are marked with the following statuses: | |
| |Technology Preview | ||
| |Technology Preview | ||
|
|
||
| |Multi-cluster Engine Operator | ||
| |Technology Preview | ||
| |Technology Preview | ||
| |Technology Preview | ||
|
|
||
| |==== | ||
|
|
||
| [discrete] | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am borrowing this from the unmerged
mainPR https://github.com/openshift/openshift-docs/pull/65963/files. Whichever merges first, this should come out in the rebase-wash.