diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md index 7cf4979e6..adb4462b8 100644 --- a/RELEASE_NOTES.md +++ b/RELEASE_NOTES.md @@ -1,6 +1,15 @@ [//]: # (Consider renaming or removing the header for next release, otherwise it appears as duplicate in the published release, e.g: https://github.com/mongodb/mongodb-enterprise-kubernetes/releases/tag/1.22.0 ) +# MCK 1.3.0 Release Notes + +## Other Changes +* Optional permissions for `PersistentVolumeClaim` moved to a separate role. When managing the operator with Helm it is possible to disable permissions for `PersistentVolumeClaim` resources by setting `operator.enablePVCResize` value to `false` (`true` by default). When enabled, previously these permissions were part of the primary operator role. With this change, permissions have a separate role. +* `subresourceEnabled` Helm value was removed. This setting used to be `true` by default and made it possible to exclude subresource permissions from the operator role by specifying `false` as the value. We are removing this configuration option, making the operator roles always have subresource permissions. This setting was introduced as a temporary solution for [this](https://bugzilla.redhat.com/show_bug.cgi?id=1803171) OpenShift issue. The issue has since been resolved and the setting is no longer needed. + + + + # MCK 1.2.0 Release Notes ## New Features @@ -28,7 +37,6 @@ ## Bug Fixes * Fixed an issue where moving a **MongoDBMultiCluster** resource to a new project (or a new OM instance) would leave the deployment in a failed state. - # MCK 1.1.0 Release Notes diff --git a/changelog/20250715_other_split_persistentvolumeclaims_rbac_into_a_separate.md b/changelog/20250715_other_split_persistentvolumeclaims_rbac_into_a_separate.md new file mode 100644 index 000000000..cd043e3d5 --- /dev/null +++ b/changelog/20250715_other_split_persistentvolumeclaims_rbac_into_a_separate.md @@ -0,0 +1,7 @@ +--- +title: Permissions for PersistentVolumeClaim moved to a separate role +kind: other +date: 2025-07-15 +--- + +* Optional permissions for `PersistentVolumeClaim` moved to a separate role. When managing the operator with Helm it is possible to disable permissions for `PersistentVolumeClaim` resources by setting `operator.enablePVCResize` value to `false` (`true` by default). When enabled, previously these permissions were part of the primary operator role. With this change, permissions have a separate role. diff --git a/changelog/20250715_other_subresourceenabled_helm_value_removed.md b/changelog/20250715_other_subresourceenabled_helm_value_removed.md new file mode 100644 index 000000000..e76796d79 --- /dev/null +++ b/changelog/20250715_other_subresourceenabled_helm_value_removed.md @@ -0,0 +1,7 @@ +--- +title: subresourceEnabled Helm value was removed +kind: other +date: 2025-07-15 +--- + +* `subresourceEnabled` Helm value was removed. This setting used to be `true` by default and made it possible to exclude subresource permissions from the operator role by specifying `false` as the value. We are removing this configuration option, making the operator roles always have subresource permissions. This setting was introduced as a temporary solution for [this](https://bugzilla.redhat.com/show_bug.cgi?id=1803171) OpenShift issue. The issue has since been resolved and the setting is no longer needed.