@@ -152,12 +152,19 @@ This release:
152
152
A migration guide for existing users will be published soon.
153
153
154
154
- Removes support for |tls| certificates in concatenated |pem| format.
155
- These certificates were deprecated in |k8s-op-short| 1.13.0. Before
156
- upgrading to |k8s-op-short| 1.17.0, migrate your |pem| files stored as
157
- :k8sdocs:`Opaque secrets </concepts/configuration/secret/#opaque-secrets>`
158
- to :k8sdocs:`kubernetes.io/tls </concepts/configuration/secret/#tls-secrets>`
159
- secrets. For detailed instructions, see
160
- :ref:`Upgrade from Kubernetes Operator 1.12 with TLS Enabled <migrate-to-new-tls-format>`.
155
+ These certificates were deprecated in |k8s-op-short| 1.13.0.
156
+ If you want to use these certificates, the last version to which you
157
+ can upgrade is |k8s-op-short| 1.16.4.
158
+
159
+ Starting with the |k8s-op-short| 1.17.0 release, you must manually
160
+ migrate old-style |tls| secrets from opaque to
161
+ :k8sdocs:`kubernetes.io/tls </concepts/configuration/secret/#tls-secrets>`
162
+ type secrets by creating new secrets that contain the relevant
163
+ certificates and signing keys. To learn how to create these secrets,
164
+ see the following resources:
165
+
166
+ - :ref:`secure-tls`
167
+ - :ref:`secure-internal-auth`
161
168
162
169
.. _ent-op-1.16.x:
163
170
@@ -187,18 +194,17 @@ MongoDB Resource
187
194
MongoDB Resource
188
195
````````````````
189
196
190
- - Fixed a bug where `securityContext defined at the Pod level wouldn't
191
- be respected as the operator would override it with a
192
- `securityContext` at the container level. See the
193
- `description <https://docs-mongodbcom-staging.corp.mongodb.com/docs-k8s-operator/docsworker-xlarge/DOCSP-23623/reference/k8s-operator-specification.html#spec.persistent>`__
194
- of the `spec.persistent` setting for more information.
197
+ - Fixed a bug where ``securityContext`` defined at the Pod level is not
198
+ respected as the |k8s-op-short| overrides it with a
199
+ ``securityContext`` at the container level. To learn more, see the
200
+ description of the :setting:`spec.persistent` setting.
195
201
196
- - Adds `timeoutMS`, and `userCacheInvalidationInterval` fields to the
197
- `spec.security.authentication.ldap` object.
202
+ - Adds `` timeoutMS`` , and `` userCacheInvalidationInterval` ` fields to the
203
+ `` spec.security.authentication.ldap` ` object.
198
204
199
- - Fixes behavior where the `additionalMongodConfig.net.tls.mode` setting
200
- was ignored for `mongos`, `configSrv`, and `shard` objects when
201
- configuring `ShardedCluster` resources.
205
+ - Fixes behavior where the `` additionalMongodConfig.net.tls.mode` ` setting
206
+ was ignored for `` mongos`` , `` configSrv`` , and `` shard` ` objects when
207
+ configuring `` ShardedCluster` ` resources.
202
208
203
209
.. _ent_op-1.16.2:
204
210
@@ -790,12 +796,12 @@ New Images
790
796
791
797
- Beginning with this release, you can use any version of MongoDB
792
798
for the Application Database. You must specify this version
793
- explicitly when you deploy the ``MongoDBOpsManager`` resource.
794
-
795
- .. include:: /includes/facts/fact-which-appdb-version.rst
799
+ explicitly when you deploy the ``MongoDBOpsManager`` resource.
796
800
797
801
- To upgrade the |k8s-op-short|, you must specify the Application
798
- Database's version. For more information, see :ref:`migrate-to-ent-appdb-version`.
802
+ Database's version. Check that the :opsmgrkube:`spec.applicationDatabase.version`
803
+ has a value in your configuration files for the ``MongoDBOpsManager``
804
+ custom resource deployment.
799
805
800
806
- Each Application Database Pod consists of the following containers
801
807
(instead of one container with a bundled MongoDB version, as in previous
0 commit comments