Skip to content

Commit 7011c68

Browse files
Merge pull request #286775 from msftadam/patch-19
Update release-notes.md
2 parents 9e1e715 + f8e1672 commit 7011c68

File tree

1 file changed

+38
-0
lines changed

1 file changed

+38
-0
lines changed

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

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,7 @@ The following release notes are generally available (GA):
2020
* Release Notes for Version 2.0.2777-132
2121
* Release Notes for Version 2.0.2783-134
2222
* Release Notes for Version 2.0.2788-135
23+
* Release Notes for Version 2.0.2804-137
2324

2425
### Release Attestation
2526
These releases are produced compliant with Microsoft’s Secure Development Lifecycle. This lifecycle includes processes for authorizing software changes, antimalware scanning, and scanning and mitigating security bugs and vulnerabilities.
@@ -180,3 +181,40 @@ The following bug fixes, or other defect resolutions, are delivered with this re
180181
#### Security Related Updates
181182

182183
None
184+
185+
## Release 2.0.2804-137
186+
187+
Document Revision 1.1
188+
189+
### Release Summary
190+
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 August 30, 2024 Azure Operator Service Manager release includes updating the NFO version to 2.0.2804-137, the details of which are further outlined in the remainder of this document.
191+
192+
### Release Details
193+
* Release Version: Version 2.0.2804-137
194+
* Release Date: August 30, 2024
195+
* Is NFO update required: YES, Update only
196+
* Dependency Versions: Go/1.22.4 - Helm/3.15.2
197+
198+
### Release Installation
199+
This release can be installed with as an update on top of release 2.0.2788-135.
200+
201+
### Release Highlights
202+
#### High availability for cluster registry and webhook.
203+
This version restores the high availability features first introduced with release 2.0.2783-134. When enabled, the singleton pod, used in earlier releases, is replaced with a replica set and optionally allows for horizontal auto scaling.
204+
205+
#### Enhanced internal certificate management and rotation.
206+
This version implements internal certificate management using a new method which does not take dependency on cert-manager. Instead, a private internal service is used to handle requirements for certificate management and rotation within the AOSM namespace.
207+
208+
#### Safe Upgrades NF Level Rollback
209+
This version introduces new user options to control behavior when a failure occurs during an upgrade. While pause on failure remains the default, a user can now optionally enable rollback on failure. If a failure occure, with rollback on failure any prior completed NfApps will be reverted to prior state using helm rollback command. See [learn documentation](safe-upgrades-nf-level-rollback.md) for more details on usage.
210+
211+
### Issues Resolved in This Release
212+
213+
#### Bugfix Related Updates
214+
The following bug fixes, or other defect resolutions, are delivered with this release, for either Network Function Operator (NFO) or resource provider (RP) components.
215+
216+
* NFO - Enhance cluster registry performance by preventing unnecessary or repeated image downloads.
217+
218+
#### Security Related Updates
219+
220+
* CVE - A total of one CVE is addressed in this release.

0 commit comments

Comments
 (0)