Release MongoDB Kubernetes Operator v0.9.0

config/manager/manager.yaml

@@ -45,7 +45,7 @@ spec:
         - name: OPERATOR_NAME
           value: mongodb-kubernetes-operator
         - name: AGENT_IMAGE
-          value: quay.io/mongodb/mongodb-agent:12.0.25.7724-1
+          value: quay.io/mongodb/mongodb-agent:107.0.0.8465-1
         - name: VERSION_UPGRADE_HOOK_IMAGE
           value: quay.io/mongodb/mongodb-kubernetes-operator-version-upgrade-post-start-hook:1.0.8
         - name: READINESS_PROBE_IMAGE

deploy/openshift/operator_openshift.yaml

@@ -47,7 +47,7 @@ spec:
         - name: OPERATOR_NAME
           value: mongodb-kubernetes-operator
         - name: AGENT_IMAGE
-          value: quay.io/mongodb/mongodb-agent:12.0.25.7724-1
+          value: quay.io/mongodb/mongodb-agent:107.0.0.8465-1
         - name: READINESS_PROBE_IMAGE
           value: quay.io/mongodb/mongodb-kubernetes-readinessprobe:1.0.17
         - name: VERSION_UPGRADE_HOOK_IMAGE

docs/RELEASE_NOTES.md

@@ -1,21 +1,7 @@
-# MongoDB Kubernetes Operator 0.8.3
+# MongoDB Kubernetes Operator 0.8.4
 
 ## MongoDBCommunity Resource
 
 - Changes
-  - Introduced support for [X.509 authentication](https://github.com/mongodb/mongodb-kubernetes-operator/blob/master/docs/x509-auth.md) for client and agent
-    - `spec.security.authentication.modes` now supports value `X509`
-    - The agent authentication mode will default to the value in `spec.security.authentication.modes` if there is only one specified.
-    - Otherwise, agent authentication will need to be specified through `spec.security.authentication.agentMode`.
-    - When agent authentication is set to `X509`, the field `spec.security.authentication.agentCertificateSecretRef` can be set (default is `agent-certs`).
-    - The secret that `agentCertificateSecretRef` points to should contain a signed X.509 certificate (under the `tls.crt` key) and a private key (under `tls.key`) for the agent.
-    - X.509 users can be added the same way as before under `spec.users`. The `db` field must be set to `$external` for X.509 authentication.
-    - For these users, `scramCredentialsSecretName` and `passwordSecretRef` should **not** be set.
-    - Sample resource [yaml](https://github.com/mongodb/mongodb-kubernetes-operator/blob/master/config/samples/mongodb.com_v1_mongodbcommunity_x509.yaml)
-    - Sample agent certificate [yaml](https://github.com/mongodb/mongodb-kubernetes-operator/blob/master/config/samples/external_access/agent-certificate.yaml)
-  - Add support for configuring [logRotate](https://www.mongodb.com/docs/ops-manager/current/reference/cluster-configuration/#mongodb-instances) on the automation-agent. The settings can be found under `processes[n].logRotate.<setting>`.
-  - Additionally, [systemLog](https://www.mongodb.com/docs/manual/reference/configuration-options/#systemlog-options) can now be configured. In particular the settings: `path`, `destination` and `logAppend`.
-  - MongoDB 7.0.0 and onwards is not supported. Supporting it requires a newer Automation Agent version. Until a new version is available, the Operator will fail all deployments with this version. To ignore this error and force the Operator to reconcile these resources, use `IGNORE_MDB_7_ERROR` environment variable and set it to `true`.
-  - Introduced support for ARM64 architecture
-    - A manifest supporting both AMD64 and ARCH64 architectures is released for each version.
-  - `ubuntu` based images are deprecated, users should move to `ubi` images next release.
+  - Introduced support for [Mongodb7](https://www.mongodb.com/docs/manual/release-notes/7.0/)
+  - Upgrading Kubernetes client APIs to 1.26

docs/how-to-release.md

@@ -1,6 +1,5 @@
 
 ## How to Release
-
 * Prepare release PR:
     * Pull the changes in the helm-charts sub module folder to get the latest main.
       * `cd helm-charts && git pull origin main`.