Skip to content

Commit

Permalink
Add OLM 1.0 relnote for 4.14
Browse files Browse the repository at this point in the history
  • Loading branch information
adellape committed Oct 18, 2023
1 parent 1c6bc03 commit 24b7898
Show file tree
Hide file tree
Showing 2 changed files with 60 additions and 13 deletions.
3 changes: 3 additions & 0 deletions _attributes/common-attributes.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -187,6 +187,9 @@ endif::[]
:osdk_ver: 1.31.0
//Operator SDK version that shipped with the previous OCP 4.x release
:osdk_ver_n1: 1.28.0
//Next-gen (OCP 4.13+) Operator Lifecycle Manager, aka "v1"
:olmv1: OLM 1.0
:olmv1-first: Operator Lifecycle Manager (OLM) 1.0
:ztp-first: GitOps Zero Touch Provisioning (ZTP)
:ztp: GitOps ZTP
:3no: three-node OpenShift
Expand Down
70 changes: 57 additions & 13 deletions release_notes/ocp-4-14-release-notes.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -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} 4.14 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:
+
--
* The `Operator` API, provided 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_.

Improved control over Operator updates::
With the greater 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}_.

[NOTE]
====
For {product-title} 4.14, 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}_.

[id="ocp-4-14-osdk"]
=== Operator development

Expand Down Expand Up @@ -786,9 +823,10 @@ In the following tables, features are marked with the following statuses:
* _Removed_

[discrete]
=== Operator deprecated and removed features
[id="ocp-4-14-operators-dep-rem"]
=== Operator lifecycle and development deprecated and removed features

.Operator deprecated and removed tracker
.Operator lifecycle and development deprecated and removed tracker
[cols="4,1,1,1",options="header"]
|====
|Feature |4.12 |4.13 |4.14
Expand Down Expand Up @@ -1703,35 +1741,36 @@ In the following tables, features are marked with the following statuses:
|====

[discrete]
=== Operator Technology Preview features
[id="ocp-4-14-operators-tech-preview"]
=== Operator lifecycle and development Technology Preview features

.Operator Technology Preview tracker
.Operator lifecycle and development Technology Preview tracker
[cols="4,1,1,1",options="header"]
|====
|Feature |4.12 |4.13 |4.14

|Hybrid Helm Operator
|Technology Preview
|Technology Preview
|Operator Lifecycle Manager (OLM) v1
|Not Available
|Not Available
|Technology Preview

|Java-based Operator
|RukPak
|Technology Preview
|Technology Preview
|Technology Preview

|Node Observability Operator
|Not Available
|Platform Operators
|Technology Preview
|Technology Preview
|Technology Preview

|Platform Operators
|Hybrid Helm Operator
|Technology Preview
|Technology Preview
|Technology Preview

|RukPak
|Not Available
|Java-based Operator
|Technology Preview
|Technology Preview
|Technology Preview

Expand Down Expand Up @@ -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]
Expand Down

0 comments on commit 24b7898

Please sign in to comment.