Merge pull request #297534 from msftadam/patch-70

Update release-notes.md

Author: prmerger-automator[bot]

articles/operator-service-manager/manage-network-function-operator.md

@@ -41,6 +41,7 @@ az k8s-extension create --cluster-name
                         [--config global.networkfunctionextension.webhook.pod.mutation.matchConditionExpression=]
                         [--config global.networkfunctionextension.clusterRegistry.clusterRegistryGCCadence=]
                         [--config global.networkfunctionextension.clusterRegistry.clusterRegistryGCThreshold=]
+                        [--config global.networkfunctionextension.clusterRegistry.registryService.scale={"small", "medium", "large"}]
                         [--version]
 ```
 
@@ -102,6 +103,17 @@ The referenced matchCondition implies that the pods getting accepted in kube-sys
 * This condition comes into play only when the CNF/Component/Application are getting installed into the namespace as per the rules and namespaceSelectors. If there are more pods getting spin up in that namespace, this condition is applied.   
 
 #### Cluster Registry
+
+> [!NOTE]
+> * When managing a NAKS cluster with AOSM, the default parameter values enable HA as the recommended configuration.
+> * When managing a AKS cluster with AOSM, HA must be disabled using the following configuration options:
+>
+>```
+>    --config global.networkfunctionextension.clusterRegistry.highAvailability.enabled=false
+>    --config global.networkfunctionextension.webhook.highAvailability.enabled=false
+>    --config global.networkfunctionextension.clusterRegistry.storageClassName=managed-csi
+>```
+
 `--config global.networkfunctionextension.enableClusterRegistry=`
 * This configuration provisions a registry in the cluster to locally cache artifacts.
 * Default values enable lazy loading mode unless global.networkfunctionextension.enableEarlyLoading=true.
@@ -111,6 +123,7 @@ The referenced matchCondition implies that the pods getting accepted in kube-sys
 `--config global.networkfunctionextension.clusterRegistry.highAvailability.enabled=`
 * This configuration provisions the cluster registry in high availability mode if cluster registry is enabled.
 * Default value is true and uses Nexus Azure kubernetes service (NAKS) nexus-shared volume on AKS recommendation is set false.
+* Registry Pod Replica Count: minimum: 3, maximum: 5
 * Accepted values: true, false.
 * Default value: true.
 
@@ -161,15 +174,21 @@ The referenced matchCondition implies that the pods getting accepted in kube-sys
 * This configuration triggers garbage collection process when cluster registry usage exceeds this value.
 * Default value: 0.
 
-> [!NOTE]
-> * When managing a NAKS cluster with AOSM, the default parameter values enable HA as the recommended configuration.
-> * When managing a AKS cluster with AOSM, HA must be disabled using the following configuration options:
->
->```
->    --config global.networkfunctionextension.clusterRegistry.highAvailability.enabled=false
->    --config global.networkfunctionextension.webhook.highAvailability.enabled=false
->    --config global.networkfunctionextension.clusterRegistry.storageClassName=managed-csi
->```
+`--config global.networkfunctionextension.clusterRegistry.registryService.scale=`
+* This configuration sets the CPU and memory resources for cluster registry to a pre-defined scale option.
+* Accetped values: small, medium, large.
+* Default value: medium.
+*  Following are the registry resource specifications for all 3 scales:
+```
+    - limits:
+      - small: cpu: 100m, memory: 2Gi
+      - medium: cpu: 500m, memory: 2Gi
+      - large: cpu: 1, memory: 4Gi
+    - requests:
+      - small: cpu: 100m, memory: 250Mi
+      - mediumL cpu: 250m, memory: 500Mi
+      - large: cpu: 500m, memory: 1Gi
+```     
 
 ## Update network function extension
 The Azure CLI command 'az k8s-extension update' is executed to update the NFO extension.

articles/operator-service-manager/release-notes.md

@@ -387,3 +387,22 @@ The following bug fixes, defect resolutions, or usability improvements are deliv
 * NFO - Cluster Registry Image Corruption Auto-Recovery [2502220010001187]: Sometimes, images in the cluster registry become corrupted due to failures during the download process. This results in all subsequent retry attempts for that image failing. This solution detects corrupted images, removes broken Docker image links, and ensures that future retries can successfully download the image.
 * NFO - Avoid performing an unnecessary image copy when the image is already present in the cluster registry: This update eliminates redundant image downloads when the Artifact Controller pod crashes or becomes temporarily unavailable due to network issues. If the image is already present in the cluster registry, the system will now bypass unnecessary copies, improving efficiency and reducing resource consumption.
 * NFO - Increase oras download concurrency count [ICM602686818]: This update increases the concurrency setting in ORAS, enhancing parallel processing and improving download speed.
+
+## Release 3.0.3007-208
+
+Document Revision 1.0
+
+### Release Summary
+Azure Operator Service Manager is a cloud orchestration service that enables automation of operator network-intensive workloads, and mission critical applications hosted on Azure Operator Nexus. Azure Operator Service Manager unifies infrastructure, software, and configuration management with a common model into a single interface, both based on trusted Azure industry standards. This March 31, 2025 Azure Operator Service Manager release includes updating the NFO version to 3.0.3007-208, the details of which are further outlined in the remainder of this document.
+
+### Release Details
+* Release Version: Version 3.0.3007-208
+* Release Date: March 31, 2025
+* Is NFO update required: YES, Update only
+* Dependency Versions: Go/1.22.4 - Helm/3.15.2
+
+#### Release Updates
+The following bug fixes, defect resolutions, or usability improvements are delivered with this release, for either Network Function Operator (NFO) or resource provider (RP) components.
+
+* NFO - [602686818] Expose new installation parameter to set cluster registry CPU and memory resources to "small", "medium" or "large" scale option.
+* NFO - [602686818] Tune ORAS concurrency settings for improved performance and resource utilization for all scale options.