Skip to content

OSDOCS#13488: OLMv1 4.19 release notes #94451

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: enterprise-4.19
Choose a base branch
from
+27 −4
Open

OSDOCS#13488: OLMv1 4.19 release notes #94451

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 27 additions & 4 deletions release_notes/ocp-4-19-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,22 @@ For more information, see xref:../edge_computing/policygenerator_for_ztp/ztp-con
[id="ocp-release-notes-extensions_{context}"]
=== Extensions ({olmv1})

[id="ocp-release-notes-olmv1-preflight-permissions-check_{context}"]
==== Preflight permissions check for cluster extensions (Technology Preview)

With this release, the Operator Controller performs a dry run of the installation process when you try to install an extension. This dry run verifies that the specified service account has the required role-based access control (RBAC) rules for the roles and bindings defined by the bundle.

If the service account is missing any required RBAC rules, the preflight check fails before the actual installation proceeds and generates a report.

For more information, see xref:../extensions/ce/managing-ce.adoc#olmv1-troubleshooting-rbac-errors-with-preflight-check_managing-ce[Preflight permissions check for cluster extensions (Technology Preview)]

[id="ocp-release-notes-olmv1-deploying-a-cluster-extension-to-a-specific-namespace_{context}"]
==== Deploying a cluster extension in a specific namespace (Technology Preview)

With this release, you can deploy an extension in a specific namespace by using the `OwnNamespace` or `SingleNamespace` install modes as a Technology Preview feature for `registry+v1` Operator bundles.

For more information, see xref:../extensions/ce/managing-ce.adoc#olmv1-deploying-a-ce-in-a-specific-namespace_managing-ce[Deploying a cluster extension in a specific namespace (Technology Preview)]

[id="ocp-release-notes-hcp_{context}"]
=== Hosted control planes

Expand Down Expand Up @@ -823,9 +839,6 @@ For more information on cgroup v2, see xref:../architecture/index.adoc#architect
[id="ocp-release-notes-openshift-cli_{context}"]
=== OpenShift CLI (oc)

[id="ocp-release-notes-olm_{context}"]
=== Operator lifecycle

[id="ocp-release-notes-osdk_{context}"]
=== Operator development

Expand Down Expand Up @@ -1349,7 +1362,7 @@ With this release, the Red{nbsp}Hat-supported version of the Operator SDK CLI to

Red{nbsp}Hat will provide bug fixes and support for versions of the Operator SDK that were released with earlier versions of {product-title} according to the link:https://access.redhat.com/product-life-cycles?product=OpenShift%20Container%20Platform%204[Product Life Cycles for {product-title} 4] (Red{nbsp}Hat Customer Portal).

Operator authors with existing Operator projects can use the version of the Operator SDK CLI tool released with {product-title} 4.18 to maintain their projects and create Operator releases targeting newer versions of {product-title}. For more information, see link:https://access.redhat.com/node/7123119[Updating the base image for existing Ansible- or Helm-based Operator projects for {product-title} 4.19 and later] (Red{nbsp}Hat Knowledgebase).
Operator authors with existing Operator projects can use link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/operators/developing-operators#osdk-about[the version of the Operator SDK CLI tool released with {product-title} 4.18] to maintain their projects and create Operator releases that target newer versions of {product-title}. For more information, see link:https://access.redhat.com/node/7123119[Updating the base image for existing Ansible- or Helm-based Operator projects for {product-title} 4.19 and later] (Red{nbsp}Hat Knowledgebase).

For more information about the unsupported, community-maintained, version of the Operator SDK, see link:https://sdk.operatorframework.io[Operator SDK (Operator Framework)].

Expand Down Expand Up @@ -1714,6 +1727,16 @@ In the following tables, features are marked with the following statuses:
|Not Available
|Technology Preview
|Technology Preview

|{olmv1} permissions preflight check for cluster extensions
|Not Available
|Not Available
|Technology Preview

|{olmv1} deploying a cluster extension in a specified namespace
|Not Available
|Not Available
|Technology Preview
|====

[discrete]
Expand Down