openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OCPBUGS 74899 Should add info in release doc about dropping cro

Browse Source
This commit is contained in:
Michael Burke
2026-02-03 09:39:22 -05:00
parent 9217801e2c
commit f09b5a23a9
3 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
modules/nodes-cluster-resource-override.adoc
View File

@@ -10,6 +10,9 @@
[role="_abstract"]
You can use the Cluster Resource Override Operator to control the level of overcommit and manage container density across all the nodes in your cluster. The Operator, which is an admission webhook, controls how nodes in specific projects can exceed defined memory and CPU limits.
:operator-name: The Cluster Resource Override Operator
include::snippets/operator-not-available.adoc[]
// Paragraph taken from 3.11 docs and modified.
// https://docs.openshift.com/container-platform/3.11/admin_guide/overcommit.html#configuring-masters-for-overcommitment
The Operator modifies the ratio between the requests and limits that are set on developer containers. In conjunction with a per-project limit range that specifies limits and defaults, you can achieve the desired level of overcommit.

2
modules/rn-ocp-release-notes-known-issues.adoc
View File

@@ -4,6 +4,8 @@
This section includes several known issues for {product-title} {product-version}.
* Currently, due to a known issue, the {product-title} 4.21 versions of the Cluster Resource Override Operator and the DPU Operator will be available in an upcoming 4.21 maintenance release. (link:https://issues.redhat.com/browse/OCPBUGS-74224[OCPBUGS-74224])
* If you mirrored the {product-title} release images to the registry of a disconnected environment by using the `oc adm release mirror` command, the release image Sigstore signature is not mirrored with the image.
+
This has become an issue in {product-title} {product-version}, because the `openshift` cluster image policy is now deployed to the cluster by default. This policy causes CRI-O to automatically verify the Sigstore signature when pulling images into a cluster. (link:https://issues.redhat.com/browse/OCPBUGS-70297[OCPBUGS-70297])

3
networking/networking_operators/dpu-operator/dpu-operator.adoc
View File

@@ -8,6 +8,9 @@ toc::[]
As a cluster administrator, you can add the DPU Operator to your cluster to manage DPU devices and network attachments.
:operator-name: The DPU Operator
include::snippets/operator-not-available.adoc[]
--
:FeatureName: The DPU Operator
include::snippets/technology-preview.adoc[]