You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/release-notes.txt
+64Lines changed: 64 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,70 @@ Release Notes for |k8s-op-full|
12
12
:depth: 1
13
13
:class: singlecol
14
14
15
+
.. _ent-op-1.32.x:
16
+
17
+
|k8s-op-full| 1.32 Series
18
+
-------------------------
19
+
20
+
.. _ent-op-1.32.0:
21
+
22
+
|k8s-op-full| 1.32.0
23
+
~~~~~~~~~~~~~~~~~~~~
24
+
25
+
*Released 2025-03-06*
26
+
27
+
New Features
28
+
````````````
29
+
30
+
- **General Availability - Multi Cluster Sharded Clusters**: Support configuring
31
+
highly available MongoDB Sharded Clusters across multiple Kubernetes clusters.
32
+
33
+
- ``MongoDB`` resources of type Sharded Cluster now support both single and
34
+
multi cluster topologies.
35
+
- The implementation is backwards compatible with single cluster deployments
36
+
of MongoDB Sharded Clusters, by defaulting ``spec.topology`` to
37
+
``SingleCluster``. Existing ``MongoDB`` resources do not need to be modified
38
+
to upgrade to this version of the |k8s-op-short|.
39
+
- Introduces support for Sharded deployments across multiple |k8s| clusters
40
+
without requiring a Service Mesh, which you can achieve by enabling all
41
+
components of such a deployment (including mongos, config servers, and mongod)
42
+
to be exposed externally to the |k8s| clusters, which enables routing
43
+
via external interfaces.
44
+
- To learn more, see the `public documentation <https://www.mongodb.com/docs/kubernetes-operator/current/reference/k8s-operator-specification/#sharded-cluster-settings>`__.
45
+
46
+
- **MongoDB**: Adds opt-out to anonymized telemetry for the |k8s-op-short|. The
47
+
data collected by telementry does not contain any Personally Identifiable
48
+
Information (PII) or even data that can be tied back to any specific customer
49
+
or company. See the `public documentation <https://www.mongodb.com/docs/kubernetes-operator/current/reference/meko-telemetry>`__ to learn more about:
50
+
51
+
- What data is included in the telemetry
52
+
- How to disable telemetry
53
+
- What RBACs are added and why they are required
54
+
55
+
- **MongoDB**: Adds a new validation to Sharded Cluster deployments to ensure
56
+
the correctness of scaling operations,. This validation restricts scaling
57
+
different components in two directions simultaneously within a single change
58
+
to the YAML file. For example, it is not allowed to add more nodes (scaling up)
59
+
to shards while simultaneously removing (scaling down) config servers or mongos.
60
+
This restriction also applies to multi-cluster deployments. A simple change
61
+
that involves "moving" one node from one cluster to another—without altering
62
+
the total number of members—will now be blocked. It is necessary to perform
63
+
a scale-up operation first and then execute a separate change for scaling down.
64
+
65
+
Bug Fixes
66
+
`````````
67
+
68
+
- Fixes the bug when status of ``MongoDBUser`` was being set to ``Updated``
69
+
prematurely. For example, new users were not immediately usable following
70
+
``MongoDBUser`` creation despite the operator reporting ``Updated`` state.
71
+
- Fixed a bug causing cluster health check issues when ordering of users and
72
+
tokens differed in Kubeconfig.
73
+
- Fixed a bug when deploying a Multi-Cluster sharded resource with an external
74
+
access configuration could result in pods not being able to reach each others.
75
+
- Fixed a bug when setting ``spec.fcv = AlwaysMatchVersion`` and ``agentAuth``
76
+
to be ``SCRAM`` causes the operator to set the auth value to be ``SCRAM-SHA-1``
0 commit comments