Skip to content

OSDOCS#10370: OLMv1 Release notes for catalog selection and proxy #88905

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

Closed
wants to merge 1 commit into from
Closed

OSDOCS#10370: OLMv1 Release notes for catalog selection and proxy #88905

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
21 changes: 20 additions & 1 deletion release_notes/ocp-4-18-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,7 @@ The updated location and guide name reflect a more focused documentation experie
====

Simplified API::
{olmv1} simplifies Operator management with a new, user-friendly API: xref:../extensions/arch/operator-controller.adoc#olmv1-clusterextension-api_operator-controller[the `ClusterExtension` object]. By managing Operators as integral extensions of the cluster, {olmv1} caters to the special lifecycle requirements of custom resource definition (CRDs). This design aligns more closely with Kubernetes principles, treating Operators, which consist of custom controllers and CRDs, as cluster-wide singletons.
{olmv1} simplifies Operator management with a new, user-friendly API: xref:../extensions/arch/operator-controller.adoc#olmv1-clusterextension-api_operator-controller[the `ClusterExtension` object]. By managing Operators as integral extensions of the cluster, {olmv1} caters to the special lifecycle requirements of custom resource definition (CRDs). This design aligns more closely with Kubernetes principles, treating Operators, which consist of custom controllers and CRDs, as cluster-wide singletons.
+
{product-title} continues to give you access to the latest Operator packages, patches, and updates through default xref:../extensions/catalogs/rh-catalogs.adoc#rh-catalogs[Red Hat Operator catalogs]. With {olmv1}, you can install an Operator package by creating and applying a `ClusterExtension` API object in your cluster. By interacting with `ClusterExtension` objects, you can manage the lifecycle of Operator packages, quickly understand their status, and troubleshoot issues.

Expand All @@ -119,6 +119,25 @@ include::snippets/olmv1-tp-extension-support.adoc[]

include::snippets/olmv1-operator-conditions-support.adoc[]

[id="ocp-4-18-extensions-catalog-selection_{context}"]
==== Improved catalog selection in {olmv1}

With this release, you can perform the following actions to control the selection of catalog content when you install or update a cluster extension:

* Specify labels to select the catalog
* Use match expressions to filter across catalogs
* Set catalog priority

For more information, see `Catalog content resolution`.

// Will update with a live link after https://github.com/openshift/openshift-docs/pull/88394 merges
// xref :../extensions/catalogs/catalog-content-resolution.adoc#catalog-content-resolution[Catalog content resolution].

[id="ocp-4-18-extensions-proxy-and-trustedCA_{context}"]
==== Basic support for proxied environments and trusted CA certificates

With this release, Operator Controller and catalogd can now run in proxied environments and include basic support for trusted CA certificates.

[id="ocp-release-notes-edge-computing_{context}"]
=== Edge computing

Expand Down