Azure/azure-service-operator (Azure/azure-service-operator)
### [`v2.9.0`](https://togithub.com/Azure/azure-service-operator/releases/tag/v2.9.0)
[Compare Source](https://togithub.com/Azure/azure-service-operator/compare/v2.8.0...v2.9.0)
#### Release notes
##### Breaking changes
##### v20230202preview ManagedCluster was removed
This removal was due to the underlying Azure API version being deprecated.
Other versions will continue to be supported. We recommend you move to use a different CRD version to avoid
seeing errors from Azure due to the 2023-02-02-preview API being deprecated. This change was performed in PR [#4182](https://togithub.com/Azure/azure-service-operator/issues/4182).
##### The RoleAssignment spec.delegatedManagedIdentityResourceId field has changed
This field was a string containing an ARM ID previously. It is now a [genruntime.ResourceReference](https://pkg.go.dev/github.com/Azure/azure-service-operator/v2/pkg/genruntime#ResourceReference).
This field is not commonly used. If your `RoleAssignment` resources don't set this field, there is no action needed.
If your cluster has `RoleAssignment` resources that set this field:
- Set the [serviceoperator.azure.com/reconcile-policy: detach-on-delete](https://azure.github.io/azure-service-operator/guide/annotations/#serviceoperatorazurecomreconcile-policy) annotation.
- Issue `kubectl delete` for those RoleAssignments. They will be deleted in ASO but not Azure.
- Upgrade ASO.
- Re-apply the `RoleAssignment` resource with the new `delegatedManagedIdentityResourceReference` field set.
##### Upcoming Breaking changes
None.
##### New resources
- Add support for new Disk API version v20240302 ([#4171](https://togithub.com/Azure/azure-service-operator/issues/4171))
- Add support for Azure RedhatOpenshift Clusters ([#4152](https://togithub.com/Azure/azure-service-operator/issues/4152))
##### Features
- Remove default operator-scoped rate limiter and add various scaling configuration options ([#4158](https://togithub.com/Azure/azure-service-operator/issues/4158))
- Add ability to configure RoleAssignments UUID generation algorithm. Allowed options are `random` and `stable` ([#4196](https://togithub.com/Azure/azure-service-operator/issues/4196))
- Allow custom OperatorSpec properties to be defined in generator configuration ([#4175](https://togithub.com/Azure/azure-service-operator/issues/4175))
##### Improvements
- Updated numerous dependencies
- Fix pre-release-test ([#4128](https://togithub.com/Azure/azure-service-operator/issues/4128))
- Update local tests and CI tests to use az login token or managed identity, not service principal ([#4003](https://togithub.com/Azure/azure-service-operator/issues/4003))
##### Bug fixes
- Fix bug where KeyVault with ARMID owner couldn't be recovered ([#4127](https://togithub.com/Azure/azure-service-operator/issues/4127))
- Fix bug where 'none' crd-management mode blocked pod start ([#4151](https://togithub.com/Azure/azure-service-operator/issues/4151))
- Fix bug where BackupVaults/BackupInstance would report ready condition before it was actually ready ([#4180](https://togithub.com/Azure/azure-service-operator/issues/4180))
- Fix bug where owner.armId could be changed ([#4193](https://togithub.com/Azure/azure-service-operator/issues/4193))
##### Documentation
- Add missing aso-controller-settings documentation ([#4160](https://togithub.com/Azure/azure-service-operator/issues/4160))
- Add contact details to our documentation site ([#4190](https://togithub.com/Azure/azure-service-operator/issues/4190))
**Full Changelog**: https://github.com/Azure/azure-service-operator/compare/v2.8.0...v2.9.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR contains the following updates:
v2.8.0->v2.9.0Release Notes
Azure/azure-service-operator (Azure/azure-service-operator)
### [`v2.9.0`](https://togithub.com/Azure/azure-service-operator/releases/tag/v2.9.0) [Compare Source](https://togithub.com/Azure/azure-service-operator/compare/v2.8.0...v2.9.0) #### Release notes ##### Breaking changes ##### v20230202preview ManagedCluster was removed This removal was due to the underlying Azure API version being deprecated. Other versions will continue to be supported. We recommend you move to use a different CRD version to avoid seeing errors from Azure due to the 2023-02-02-preview API being deprecated. This change was performed in PR [#4182](https://togithub.com/Azure/azure-service-operator/issues/4182). ##### The RoleAssignment spec.delegatedManagedIdentityResourceId field has changed This field was a string containing an ARM ID previously. It is now a [genruntime.ResourceReference](https://pkg.go.dev/github.com/Azure/azure-service-operator/v2/pkg/genruntime#ResourceReference). This field is not commonly used. If your `RoleAssignment` resources don't set this field, there is no action needed. If your cluster has `RoleAssignment` resources that set this field: - Set the [serviceoperator.azure.com/reconcile-policy: detach-on-delete](https://azure.github.io/azure-service-operator/guide/annotations/#serviceoperatorazurecomreconcile-policy) annotation. - Issue `kubectl delete` for those RoleAssignments. They will be deleted in ASO but not Azure. - Upgrade ASO. - Re-apply the `RoleAssignment` resource with the new `delegatedManagedIdentityResourceReference` field set. ##### Upcoming Breaking changes None. ##### New resources - Add support for new Disk API version v20240302 ([#4171](https://togithub.com/Azure/azure-service-operator/issues/4171)) - Add support for Azure RedhatOpenshift Clusters ([#4152](https://togithub.com/Azure/azure-service-operator/issues/4152)) ##### Features - Remove default operator-scoped rate limiter and add various scaling configuration options ([#4158](https://togithub.com/Azure/azure-service-operator/issues/4158)) - Add ability to configure RoleAssignments UUID generation algorithm. Allowed options are `random` and `stable` ([#4196](https://togithub.com/Azure/azure-service-operator/issues/4196)) - Allow custom OperatorSpec properties to be defined in generator configuration ([#4175](https://togithub.com/Azure/azure-service-operator/issues/4175)) ##### Improvements - Updated numerous dependencies - Fix pre-release-test ([#4128](https://togithub.com/Azure/azure-service-operator/issues/4128)) - Update local tests and CI tests to use az login token or managed identity, not service principal ([#4003](https://togithub.com/Azure/azure-service-operator/issues/4003)) ##### Bug fixes - Fix bug where KeyVault with ARMID owner couldn't be recovered ([#4127](https://togithub.com/Azure/azure-service-operator/issues/4127)) - Fix bug where 'none' crd-management mode blocked pod start ([#4151](https://togithub.com/Azure/azure-service-operator/issues/4151)) - Fix bug where BackupVaults/BackupInstance would report ready condition before it was actually ready ([#4180](https://togithub.com/Azure/azure-service-operator/issues/4180)) - Fix bug where owner.armId could be changed ([#4193](https://togithub.com/Azure/azure-service-operator/issues/4193)) ##### Documentation - Add missing aso-controller-settings documentation ([#4160](https://togithub.com/Azure/azure-service-operator/issues/4160)) - Add contact details to our documentation site ([#4190](https://togithub.com/Azure/azure-service-operator/issues/4190)) **Full Changelog**: https://github.com/Azure/azure-service-operator/compare/v2.8.0...v2.9.0Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.