File tree Expand file tree Collapse file tree 4 files changed +58
-7
lines changed Expand file tree Collapse file tree 4 files changed +58
-7
lines changed Original file line number Diff line number Diff line change 120120 '.. |global-write-cluster| replace:: Global Cluster' ,
121121 '.. |global-write| replace:: Global Writes' ,
122122 '.. |hardlink| replace:: https://docs.mongodb.com/kubernetes-operator/' ,
123- '.. |https| replace:: :abbr:`HTTPS (Secure HyperText Transport Protocol)`' ,
124- '.. |http| replace:: :abbr:`HTTP (HyperText Transport Protocol)`' ,
123+ '.. |https| replace:: :abbr:`HTTPS (Hypertext Transfer Protocol Secure )`' ,
124+ '.. |http| replace:: :abbr:`HTTP (Hypertext Transfer Protocol)`' ,
125125 '.. |iana| replace:: :abbr:`IANA (Internet Assigned Numbers Authority)`' ,
126126 '.. |iops| replace:: :abbr:`IOPS (Input/Output Operations per Second)`' ,
127127 '.. |ipaddr| replace:: :abbr:`IP (Internet Protocol)`' ,
Original file line number Diff line number Diff line change @@ -102,6 +102,32 @@ If the |k8s-op-short| and resources sit in the same ``mongodb``
102102This would mean that it could not clean the configurations, which
103103would have to be done in the |application|.
104104
105+ .. _https-enablement-issues:
106+
107+ HTTPS Enabled After Deployment
108+ ------------------------------
109+
110+ We recommend that you enable |https| *before* deploying your |onprem| resources.
111+ However, if you enable |https| after deployment,
112+ your managed resources can no longer communicate with |onprem| and
113+ the |k8s-op-short| reports your resources' status as ``Failed``.
114+
115+ To resolve this issue, you must delete your |k8s-pods| by
116+ running the following command for each Pod:
117+
118+ .. code-block:: sh
119+
120+ kubectl delete pod <replicaset-pod-name>
121+
122+ After deletion, |k8s| automatically restarts the deleted Pods.
123+ During this period, the resource is unreachable and incurs
124+ downtime.
125+
126+ .. seealso::
127+
128+ - :ref:`config-https`
129+ - :ref:`k8s-troubleshooting`
130+
105131Difficulties with Updates
106132-------------------------
107133
Original file line number Diff line number Diff line change @@ -606,6 +606,19 @@ default permissions.
606606
607607 :ref:`meko-om-arch`
608608
609+ Enable HTTPS
610+ ------------
611+
612+ The |k8s-op-short| supports configuring |onprem| to run over
613+ :ref:`HTTPS <config-https>`.
614+
615+ Enable |https| before deploying your |onprem| resources to avoid a situation
616+ where the |k8s-op-short| reports your resources' status as ``Failed``.
617+
618+ .. seealso::
619+
620+ - :ref:`https-enablement-issues`
621+
609622Enable TLS
610623----------
611624
@@ -737,4 +750,4 @@ Example User CRD
737750
738751 - :setting:`spec.security.authentication.ldap.automationLdapGroupDN`
739752 - :ref:`Manage Database Users Using X.509 Authentication <create-x509-certs>`
740- - :ref:`Manage Database Users Using SCRAM Authentication <add-db-user-scram>`
753+ - :ref:`Manage Database Users Using SCRAM Authentication <add-db-user-scram>`
Original file line number Diff line number Diff line change @@ -253,15 +253,27 @@ To disable backup after you enabled it:
253253 To learn about reclaiming |k8s-pvs|, see the
254254 :k8sdocs:`Kubernetes documentation </concepts/storage/persistent-volumes/#reclaiming>`.
255255
256+ .. _config-https:
257+
256258Configure |onprem| to Run over HTTPS
257259~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
258260
259- You can configure an instance |onprem| created through the
260- |k8s-op-short| to run over |https|, rather than |http|. To configure
261- your |onprem| instance to run over |https|, you must provide a |tls|
262- certificate and Private Key in the |onprem| configuration object.
261+ You can configure your |onprem| instance created through the |k8s-op-short|
262+ to run over |https| instead of |http|.
263+
264+ To configure your |onprem| instance to run over |https|, provide a |tls|
265+ certificate and Private Key in the |onprem| configuration object.
266+
263267For detailed instructions, see :ref:`deploy-om-container`.
264268
269+ .. important::
270+
271+ If you have existing deployments, you must restart them manually
272+ after enabling |https|. To avoid restarting your deployments,
273+ configure |https| before deploying your managed resources.
274+
275+ To learn more, see :ref:`https-enablement-issues`.
276+
265277Ops Manager Application Access
266278~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
267279
You can’t perform that action at this time.
0 commit comments