@@ -719,3 +719,71 @@ To check whether a MongoDB binary folder is present:
719
719
`copy the MongoDB archive
720
720
<../tutorial/deploy-om-container-local-mode.html#copy-the-mongodb-archive-to-the-onprem-persistent-volume>`__
721
721
into the |onprem| Persistent Volume for each deployed |onprem| replica set.
722
+
723
+ Upgrade Fails Using ``kubectl`` or ``oc``
724
+ -----------------------------------------
725
+
726
+ .. include:: /includes/facts/upgrade-error.rst
727
+
728
+ To resolve this error:
729
+
730
+ a. Remove the old |k8s-op-short| deployment.
731
+
732
+ .. include:: /includes/facts/k8s-remove-operator-deployment.rst
733
+
734
+ .. include:: /includes/admonitions/remove-op-no-affect-mdb.rst
735
+
736
+ b. Repeat the ``kubectl apply`` command to upgrade to the new
737
+ version of the |k8s-op-short|.
738
+
739
+ Upgrade Fails Using Helm Charts
740
+ -------------------------------
741
+
742
+ .. include:: /includes/facts/upgrade-error-helm.rst
743
+
744
+ To resolve this error:
745
+
746
+ a. Remove the old |k8s-op-short| deployment.
747
+
748
+ .. include:: /includes/facts/k8s-remove-operator-deployment.rst
749
+
750
+ .. include:: /includes/admonitions/remove-op-no-affect-mdb.rst
751
+
752
+ b. Repeat the ``helm`` command to upgrade to the new version of the
753
+ |k8s-op-short|.
754
+
755
+ Two Operator Instances After an Upgrade
756
+ ---------------------------------------
757
+
758
+ After you upgrade from |k8s-op-short| version 1.10 or earlier to a
759
+ version 1.11 or later, your |k8s| cluster might have two instances of
760
+ the |k8s-op-short| deployed.
761
+
762
+ Use the ``get pods`` command to view your |k8s-op-short| pods:
763
+
764
+ .. note::
765
+
766
+ If you deployed the |k8s-op-short| to OpenShift, replace the
767
+ ``kubectl`` commands in this section with ``oc`` commands.
768
+
769
+ .. code-block:: sh
770
+
771
+ kubectl get pods
772
+
773
+ If the response contains both an ``enterprise-operator`` and a
774
+ ``mongodb-enterprise-operator`` pod, your cluster has two |k8s-op-short|
775
+ instances:
776
+
777
+ .. code-block:: sh
778
+ :copyable: false
779
+
780
+ NAME READY STATUS RESTARTS AGE
781
+ enterprise-operator-767884c9b4-ltkln 1/1 Running 0 122m
782
+ mongodb-enterprise-operator-6d69686679-9fzs7 1/1 Running 0 68m
783
+
784
+ You can safely remove the ``enterprise-operator`` deployment. Run the
785
+ following command to remove it:
786
+
787
+ .. code-block:: sh
788
+
789
+ kubectl delete deployment/enterprise-operator
0 commit comments