Skip to content

Commit

Permalink
Add OLM v1 relnote for 4.14
Browse files Browse the repository at this point in the history
  • Loading branch information
adellape committed Aug 15, 2023
1 parent 1bf4d74 commit f552f24
Showing 1 changed file with 23 additions and 1 deletion.
24 changes: 23 additions & 1 deletion release_notes/ocp-4-14-release-notes.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -173,6 +173,28 @@ With this release, {product-title} updated to HAProxy 2.6.
[id="ocp-4-14-olm"]
=== Operator lifecycle

[id="ocp-4-14-olmv1"]
=== Operator Lifecycle Manager v1 (Technology Preview)

{product-title} 4.14 introduces components for a next-generation iteration of Operator Lifecycle Manager (OLM) as a Technology Preview feature. Known during this phase as OLM v1, the updated framework evolves many of the concepts that have been part of the version of OLM included in OpenShift Container Platform up to this point, referred to retroactively as OLM v0.

OLM v1 improves Operator and extension lifecycle management in the following areas:

* Dependencies and constraints
* Tenant isolation
* Simplified packaging models
* Multi-cluster support

In OLM v1, a _plain bundle_ is a static collection of arbitrary Kubernetes manifests in the YAML format. In the Technology Preview phase, cluster administrators and Operator catalog maintainers can build and publish a file-based catalog that includes a plain bundle image by completing the following procedures:

. Build a plain bundle image.
. Create a file-based catalog.
. Add the plain bundle image to your file-based catalog.
. Build your catalog as an image.
. Publish your catalog image.

For more information, see "Managing catalogs for OLM v1".

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

Expand Down Expand Up @@ -214,7 +236,7 @@ For further information about gathering debugging information relating to low-la

[id="ocp-4-14-nw-ipv6-spoke-cluster-support"]
==== Support for provisioning IPv6 spoke clusters from dual-stack hub clusters
With this update, you can provision IPv6 address spoke clusters from dual-stack hub clusters. In a zero touch provisioning (ZTP) environment, the HTTP server on the hub cluster that hosts the boot ISO now listens on both IPv4 and IPv6 networks. The provisioning service also checks the baseboard management controller (BMC) address scheme on the target spoke cluster and provides a matching URL for the installation media. These updates offer the ability to provision single-stack, IPv6 spoke clusters from a dual-stack hub cluster.
With this update, you can provision IPv6 address spoke clusters from dual-stack hub clusters. In a zero touch provisioning (ZTP) environment, the HTTP server on the hub cluster that hosts the boot ISO now listens on both IPv4 and IPv6 networks. The provisioning service also checks the baseboard management controller (BMC) address scheme on the target spoke cluster and provides a matching URL for the installation media. These updates offer the ability to provision single-stack, IPv6 spoke clusters from a dual-stack hub cluster.

[id="ocp-4-14-hcp"]
=== Hosted control planes (Technology Preview)
Expand Down

0 comments on commit f552f24

Please sign in to comment.