Skip to content

OSDOCS-12713 CVO log levels release note #100340

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

Merged
merged 1 commit into from
Oct 15, 2025
Merged

OSDOCS-12713 CVO log levels release note #100340

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
18 changes: 15 additions & 3 deletions release_notes/ocp-4-20-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -470,6 +470,13 @@ Starting in {product-title} 4.14, Extended Update Support (EUS) is extended to t
[id="ocp-release-notes-installation-and-update_{context}"]
=== Installation and update

[id="ocp-4-20-install-update-cvo-log-levels_{context}"]
==== Changing the CVO log level (Technology Preview)

With this release, the Cluster Version Operator (CVO) log level verbosity can be changed by the cluster administrator.

For more information, see xref:../updating/troubleshooting_updates/gathering-data-cluster-update.adoc#changing-log-data_gathering-data-cluster-update[Changing CVO log level].

[id="ocp-4-20-installation-and-update-vsphere-multiple-nics_{context}"]
==== Installing a cluster on {vmw-full} with multiple network interface controllers (Generally Available)

Expand Down Expand Up @@ -801,15 +808,15 @@ For more information, see xref:../updating/updating_a_cluster/updating-cluster-c
include::snippets/osdk-release-notes-operator-images.adoc[]

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

[id="ocp-release-notes-olm-operatorhub-rename_{context}"]
==== Red{nbsp}Hat Operator catalogs moved from OperatorHub to the software catalog in the console

With this release, the Red{nbsp}Hat-provided Operator catalogs have moved from OperatorHub to the software catalog and the *Operators* navigation item is renamed to *Ecosystem* in the console. The unified software catalog presents Operators, Helm charts, and other installable content in the same console view.

* To access the Red{nbsp}Hat-provided Operator catalogs in the console, select *Ecosystem* -> *Software Catalog*.
* To manage, update, and remove installed Operators, select *Ecosystem* -> *Installed Operators*.
* To manage, update, and remove installed Operators, select *Ecosystem* -> *Installed Operators*.

[NOTE]
====
Expand Down Expand Up @@ -844,7 +851,7 @@ For more information, see xref:../scalability_and_performance/cnf-numa-aware-sch

With this release, the NUMA Resources Operator can now manage control plane nodes that are configured as schedulable. This capability allows you to deploy topology-aware workloads on control plane nodes, which is especially useful in resource-constrained environments like compact clusters.

This enhancement helps the NUMA Resources Operator schedule your NUMA-aware pods on the node with the most suitable NUMA topology, even on control plane nodes.
This enhancement helps the NUMA Resources Operator schedule your NUMA-aware pods on the node with the most suitable NUMA topology, even on control plane nodes.

For more information, see xref:../scalability_and_performance/cnf-numa-aware-scheduling.adoc#cnf-numa-resource-operator-support-scheduling-cp_numa-aware[NUMA Resources Operator support for schedulable control-plane nodes].

Expand Down Expand Up @@ -1577,6 +1584,11 @@ In the following tables, features are marked with the following statuses:
|Not Available
|Technology Preview
|Technology Preview

|Changing the CVO log level
|Not Available
|Not Available
|Technology Preview
|====


Expand Down