From 6f2df6621f4bcc0f5e0a21125045110e854dd475 Mon Sep 17 00:00:00 2001 From: Andrea Hoffer Date: Tue, 25 Jun 2024 12:03:26 -0400 Subject: [PATCH] Adding notable technical change for builder sa --- release_notes/ocp-4-16-release-notes.adoc | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/release_notes/ocp-4-16-release-notes.adoc b/release_notes/ocp-4-16-release-notes.adoc index fbdc362317..1c2da6c305 100644 --- a/release_notes/ocp-4-16-release-notes.adoc +++ b/release_notes/ocp-4-16-release-notes.adoc @@ -877,7 +877,7 @@ The Telemetry and the Insights Operator collects telemetry on IPsec connections. [id="overlapping-ip-configuration-multi-tenant-networks-whereabouts"] ==== Overlapping IP configuration for multi-tenant networks with Whereabouts -Previously, it was not possible to configure the same CIDR range twice and to have the Whereabouts CNI plugin assign IP addresses from these ranges independently. This limitation caused issues in multi-tenant environments where different groups might need to select overlapping CIDR ranges. +Previously, it was not possible to configure the same CIDR range twice and to have the Whereabouts CNI plugin assign IP addresses from these ranges independently. This limitation caused issues in multi-tenant environments where different groups might need to select overlapping CIDR ranges. With this release, the Whereabouts CNI plugin supports overlapping IP address ranges through the inclusion of a `network_name` parameter. Administrators can use the `network_name` parameter to configure the same CIDR range multiple times within separate `NetworkAttachmentDefinitions`, which enables independent IP address assignments for each range. @@ -1373,6 +1373,14 @@ In {product-title} 4.16, {olmv1-first} changes its default upgrade constraints f For more information, see xref:../release_notes/ocp-4-16-release-notes.adoc#ocp-4-16-olmv1-legacy-olm-upgrade-edges_release-notes[Support for {olmv0} upgrade edges in {olmv1} (Technology Preview)]. +[discrete] +[id="ocp-4-16-builder-sa"] +=== The builder service account is no longer created if the Build cluster capability is disabled + +With this release, if you disable the `Build` cluster capability, the `builder` service account and its corresponding secrets are no longer created. + +For more information, see xref:../installing/cluster-capabilities.adoc#build-config-capability_cluster-capabilities[Build capability]. + [id="ocp-4-16-deprecated-removed-features_{context}"] == Deprecated and removed features @@ -2421,7 +2429,7 @@ To retain the catalog rebuilding functionality, use `--rebuild-catalog`. However * Previously, when running a cluster with FIPS enabled, you might have received the following error when running the {oc-first} on a {op-system-base} 9 system: `FIPS mode is enabled, but the required OpenSSL backend is unavailable`. With this release, the default version of OpenShift CLI (`oc`) is compiled with {op-system-base-full} 9 and works properly when running a cluster with FIPS enabled on {op-system-base} 9. Additionally, a version of `oc` compiled with {op-system-base} 8 is also provided, which must be used if you are running a cluster with FIPS enabled on {op-system-base} 8. (link:https://issues.redhat.com/browse/OCPBUGS-23386[*OCPBUGS-23386*], link:https://issues.redhat.com/browse/OCPBUGS-28540[*OCPBUGS-28540*]) -* Previously, role bindings related to the `ImageRegistry`, `Build`, and `DeploymentConfig` capabilities were created in every namespace, even if the capability was disabled. With this release, the role bindings are only created if the cluster capability is enabled on the cluster. (link:https://issues.redhat.com/browse/OCPBUGS-34384[*OCPBUGS-34384*]) +* Previously, role bindings related to the `ImageRegistry` and `Build` capabilities were created in every namespace, even if the capability was disabled. With this release, the role bindings are only created if the respective cluster capability is enabled on the cluster. (link:https://issues.redhat.com/browse/OCPBUGS-34384[*OCPBUGS-34384*]) [discrete] [id="ocp-4-16-olm-bug-fixes_{context}"] @@ -3200,7 +3208,7 @@ metadata: data: mtu: "1500" <1> ---- -<1> The `mtu` value must be aligned with the MTU of the node interface. +<1> The `mtu` value must be aligned with the MTU of the node interface. + (link:https://issues.redhat.com//browse/OCPBUGS-35316[*OCPBUGS-35316*])