@@ -12,6 +12,61 @@ Release Notes for |k8s-op-full|
1212 :depth: 1
1313 :class: singlecol
1414
15+ .. _ent-op-1.3.0:
16+
17+ |k8s-op-full| 1.3.0
18+ -------------------
19+
20+ *Released 2019-10-25*
21+
22+ .. important::
23+
24+ This release introduces significant changes that may not be
25+ compatible with previous deployments or resource configurations. Read
26+ :doc:`/tutorial/migrate-to-single-resource` before installing or
27+ upgrading the |k8s-op-short|.
28+
29+ Specification Schema Changes
30+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
31+
32+ - Moves to a
33+ :doc:`one cluster per project configuration </tutorial/migrate-to-single-resource>`.
34+ This follows the warnings introduced in a
35+ :ref:`previous version of the operator <ent-op-1.2.3>`.
36+ The operator now requires each cluster to be contained within a new
37+ project.
38+
39+ - Authentication settings are now contained within the
40+ :ref:`security section <security-settings>` of the MongoDB resource
41+ specification rather than the project ConfigMap.
42+
43+ - Replaces the ``project`` field with the
44+ :setting:`spec.opsManager.configMapRef.name` or
45+ :setting:`spec.cloudManager.configMapRef.name` fields.
46+
47+ - :ref:`User resources <manage-db-users>` now refer to MongoDB resources
48+ rather than project ConfigMaps.
49+
50+ - No longer requires ``data.projectName`` in the project ConfigMap. The
51+ name of the project defaults to the name of the MongoDB resource in
52+ |k8s|.
53+
54+ Ops Manager Resource Changes
55+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
56+
57+ This release introduces signficant changes to the |onprem| resource's
58+ architecture. The |onprem| application database is now managed by
59+ the |k8s-op-short|, not by |onprem|.
60+
61+ Bug Fixes
62+ ~~~~~~~~~
63+
64+ - Stops unnecessary recreation of NodePorts.
65+
66+ - Fixes logging so it's always in JSON format.
67+
68+ - Sets ``USER`` in the |k8s-op-short| Docker image.
69+
1570.. _ent-op-1.2.4:
1671
1772|k8s-op-full| 1.2.4
0 commit comments