(DOCSP-7616): Release Notes for v1.3.1 (#126)

* (DOCSP-7616): Release Notes for v1.3.1

* (DOCSP-7616): small fixes/links

* (DOCSP-7616): Copy review

* (DOCSP-7616): Remove security fix, add alpha release note

* (DOCSP-7616): Add admonition

Author: melissamahoney-mongodb

source/includes/fact-one-cluster-per-proj.rst

@@ -1,3 +1,4 @@
-Starting in |k8s-op-full| version 1.3.0, you can only have one MongoDB
-resource per project. To learn how to migrate your project to a
-single-cluster configuration, see :ref:`migrate-single-cluster`.
+Starting in |k8s-op-full| version 1.3.0, you can only have one
+MongoDB resource per project. To learn how to migrate your project to
+a single-cluster configuration, see :ref:`migrate-single-cluster`.
+   

source/release-notes.txt

@@ -12,6 +12,51 @@ Release Notes for |k8s-op-full|
    :depth: 1
    :class: singlecol
 
+.. _ent-op-1.3.1:
+
+|k8s-op-full| 1.3.1
+-------------------
+
+*Released 2019-11-08*
+
+.. important::
+
+   This release introduces significant changes that may not be 
+   compatible with previous deployments or resource configurations. Read
+   :doc:`/tutorial/migrate-to-single-resource` before 
+   upgrading the |k8s-op-short|.
+
+MongoDB Resource Changes
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+- Requires one MongoDB resource per |onprem| project. If you
+  have more than one MongoDB resource in a project, all resources will
+  change to a ``Pending`` status and the |k8s-op-short| won’t perform
+  any changes on them. The existing MongoDB databases will still be
+  accessible. You must :ref:`migrate to one resource per project
+  <migrate-single-cluster>`.
+
+- Supports ``SCRAM-SHA`` authentication mode. See :gh:`the MongoDB
+  Enterprise Kubernetes Operator GitHub repository
+  </mongodb/mongodb-enterprise-kubernetes/tree/master/samples/extended/authentication/scram>`
+  for examples.
+
+- Requires that the project (:ref:`ConfigMap <create-k8s-project>`) and
+  credentials (:ref:`secret <create-k8s-secret>`) 
+  referenced from a MongoDB resource be in the same namespace.
+
+- Adds OpenShift installation files (|yaml| file and Helm chart
+  configuration).
+
+
+Ops Manager Resource Changes (Alpha Release)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- Supports highly available :ref:`Ops Manager resources
+  <k8s-om-specification>` by introducing the ``spec.replicas`` setting.
+
+- Runs |k8s-pods| as a non-root user.
+
 .. _ent-op-1.3.0:
 
 |k8s-op-full| 1.3.0
@@ -51,8 +96,8 @@ Specification Schema Changes
   name of the project defaults to the name of the MongoDB resource in
   |k8s|.
 
-Ops Manager Resource Changes
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Ops Manager Resource Changes (Alpha Release)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 This release introduces signficant changes to the |onprem| resource's
 architecture. The |onprem| application database is now managed by
@@ -153,8 +198,9 @@ Alpha Release
 
 This feature is an alpha release. It is not ready for production use.
 
-- Can use the |k8s-op-short| to manage |onprem| 4.2. To deploy an
-  |onprem| instance, you use a new Resource: ``MongoDBOpsManager``.
+- Can use the |k8s-op-short| to manage |onprem| 4.2. To :doc:`deploy an
+  |onprem| instance </tutorial/deploy-om-container>`, you use a new
+  :ref:`resource <k8s-om-specification>`: ``MongoDBOpsManager``.
 
 .. _ent-op-1.1:
 

source/tutorial/upgrade-k8s-operator.txt

@@ -16,12 +16,13 @@ Upgrade the Operator
 
 .. include:: /includes/styles/corrections.rst
 
+.. admonition:: Upgrading to version 1.3.0 and newer
+   :class: warning
+
+   .. include:: /includes/fact-one-cluster-per-proj.rst
+
 Procedure
 ---------
 
 .. include:: /includes/upgrade-k8s-operator.rst
 
-Additional Considerations for Version 1.3.0
--------------------------------------------
-
-.. include:: /includes/fact-one-cluster-per-proj.rst