Merge pull request #71447 from bergerhoffer/OSDOCS-8972-rn

OSDOCS#8972: Release note for disabling DC capability not generating …

Author: bergerhoffer

release_notes/ocp-4-15-release-notes.adoc

@@ -93,7 +93,7 @@ For more information, see xref:../installing/installing_nutanix/nutanix-failure-
 {product-title} {product-version} now supports the ability to enable 64k page sizes in the {op-system} kernel using the Machine Config Operator (MCO). This setting is exclusive to machines with 64-bit ARM architectures. For more information, see the xref:../post_installation_configuration/machine-configuration-tasks.adoc#machine-configuration-tasks[Machine configuration tasks] documentation.
 
 [id="ocp-4-15-installation-and-update-optional-olm"]
-==== Optional OLM cluster capability 
+==== Optional OLM cluster capability
 In {product-title} 4.15, you can disable the Operator Lifecycle Manager (OLM) capability during installation. For further information, see xref:../installing/cluster-capabilities.adoc#olm-overview_cluster-capabilities[Operator Lifecycle Manager capability].
 
 [id="ocp-4-15-deploying-osp-with-root-volume-etcd-on-local-disk"]
@@ -507,7 +507,7 @@ This feature provides support for deploying {lvms} on multi-node clusters. Prior
 [WARNING]
 ====
 {lvms} only supports node local storage on multi-node clusters. It does not support storage data replication mechanism across nodes. When using {lvms} on multi-node clusters, you must ensure storage data replication through active or passive replication mechanisms to avoid a single point of failure.
-==== 
+====
 
 For more information, see xref:../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#lvms-preface-sno-ran_logical-volume-manager-storage[Deploying {lvms}].
 
@@ -655,7 +655,7 @@ For more information, see xref:../monitoring/config-map-reference-for-the-cluste
 
 [id="ocp-4-15-monitoring-improved-alert-querying-for-user-defined-projects"]
 ==== Improved alert querying for user-defined projects
-Applications in user-defined projects now have API access to query alerts for application namespaces via the rules tenancy port for Thanos Querier. 
+Applications in user-defined projects now have API access to query alerts for application namespaces via the rules tenancy port for Thanos Querier.
 You can now construct queries that access the `/api/v1/alerts` endpoint via port 9093 for Thanos Querier, provided that the HTTP request contains a `namespace` parameter.
 In previous releases, the rules tenancy port for Thanos Querier did not provide API access to the `/api/v1/alerts` endpoint.
 
@@ -772,21 +772,21 @@ If you are receiving pod security violations, see the following resources:
 
 [discrete]
 [id="ocp-4-15-auth-generated-secrets"]
-==== Secrets are no longer automatically generated when the integrated {product-registry} is disabled
+=== Secrets are no longer automatically generated when the integrated {product-registry} is disabled
 
-If you disable the `ImageRegistry` capability or if you disable the integrated {product-registry} in the Cluster Image Registry Operator's configuration, a service account token secret and image pull secret are no longer generated for each service account.
+If you disable the `ImageRegistry` cluster capability or if you disable the integrated {product-registry} in the Cluster Image Registry Operator's configuration, a service account token secret and image pull secret are no longer generated for each service account.
 
 For more information, see xref:../nodes/pods/nodes-pods-secrets.adoc#auto-generated-sa-token-secrets_nodes-pods-secrets[Automatically generated secrets].
 
 [discrete]
 [id="ocp-4-15-ovnic-default-range"]
-==== Open Virtual Network Infrastructure Controller default range
+=== Open Virtual Network Infrastructure Controller default range
 
 Previously, the IP address range `168.254.0.0/16` was the default IP address range that the Open Virtual Network Infrastructure Controller used for the transit switch subnet. With this update, the Controller uses `100.88.0.0/16` as the default IP address range. Do not use this IP range in your production infrastructure network. (link:https://issues.redhat.com/browse/OCPBUGS-20178[*OCPBUGS-20178*])
 
 [discrete]
 [id="ocp-4-15-no-strict-limits-variable"]
-==== Introduction of HAProxy no strict-limits variable
+=== Introduction of HAProxy no strict-limits variable
 
 The transition to HAProxy 2.6 included enforcement for the `strict-limits` configuration, which resulted in fatal errors when `maxConnections` requirements could not be met. The `strict-limits` setting is not configurable by end users and remains under the control of the HAProxy template.
 
@@ -797,6 +797,14 @@ This release introduces a configuration adjustment in response to the transition
 
 To resolve these warnings, we recommend specifying `-1` or `auto` for the `maxConnections` field when tuning an IngressController. This choice allows HAProxy to dynamically calculate the maximum value based on the available resource limitations in the running container, which eliminates these warnings. (https://issues.redhat.com/browse/OCPBUGS-21803[*OCPBUGS-21803*])
 
+[discrete]
+[id="ocp-4-15-auth-deployer-sa"]
+=== The deployer service account is no longer created if the DeploymentConfig cluster capability is disabled
+
+If you disable the `DeploymentConfig` cluster capability, the `deployer` service account and its corresponding secrets are no longer created.
+
+For more information, see xref:../installing/cluster-capabilities.adoc#deployment-config-capability_cluster-capabilities[DeploymentConfig capability].
+
 [id="ocp-4-15-deprecated-removed-features"]
 == Deprecated and removed features