OCPBUGS-499969: Removed 4.10 and 4.11 references from MetalLB docs

Author: dfitzmau

modules/olm-updating-metallb-operatorgroup.adoc

@@ -6,10 +6,10 @@
 [id="olm-updating-metallb-operatorgroup_{context}"]
 = Editing the MetalLB Operator Operator group
 
-When upgrading from any MetalLB Operator version up to and including 4.10 to 4.11 and later, remove `spec.targetNamespaces` from the Operator group custom resource (CR). You must remove the spec regardless of whether you used the web console or the CLI to delete the MetalLB Operator.
+When upgrading from any MetalLB Operator version, remove `spec.targetNamespaces` from the Operator group custom resource (CR). You must remove the spec regardless of whether you used the web console or the CLI to delete the MetalLB Operator.
 [NOTE]
 ====
-The MetalLB Operator version 4.11 or later only supports the `AllNamespaces` install mode, whereas 4.10 or earlier versions support `OwnNamespace` or `SingleNamespace` modes.
+The MetalLB Operator only supports the `AllNamespaces` install mode.
 ====
 
 .Prerequisites

networking/networking_operators/metallb-operator/metallb-upgrading-operator.adoc

@@ -6,29 +6,9 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-If you are currently running version 4.10 or an earlier version of the MetalLB Operator, please note that automatic updates to any version later than 4.10 do not work. Upgrading to a newer version from any version of the MetalLB Operator that is 4.11 or later is successful. For example, upgrading from version 4.12 to version 4.13 will occur smoothly.
+You can upgrade from an earlier version of the MetalLB Operator to a newer version. 
 
-A summary of the upgrade procedure for the MetalLB Operator from 4.10 and earlier is as follows:
-
-. Delete the installed MetalLB Operator version for example 4.10. Ensure that the namespace and the `metallb` custom resource are not removed.
-
-. Using the CLI, install the MetalLB Operator {product-version} in the same namespace where the previous version of the MetalLB Operator was installed.
-
-[NOTE]
-====
-This procedure does not apply to automatic z-stream updates of the MetalLB Operator, which follow the standard straightforward method.
-====
-
-For detailed steps to upgrade the MetalLB Operator from 4.10 and earlier, see the guidance that follows. As a cluster administrator, start the upgrade process by deleting the MetalLB Operator by using the OpenShift CLI (`oc`) or the web console.
-
-//Delete metallb using web console
-include::modules/olm-deleting-metallb-operators-from-a-cluster-using-web-console.adoc[leveloffset=+1]
-
-//Delete metallb using cli
-include::modules/olm-deleting-metallb-operators-from-a-cluster-using-cli.adoc[leveloffset=+1]
-
-//Delete targetNamespace
-include::modules/olm-updating-metallb-operatorgroup.adoc[leveloffset=+1]
+As a cluster administrator, start the upgrade process by deleting the MetalLB Operator by using the OpenShift CLI (`oc`) or the web console.
 
 //Upgrade the MetalLB
 include::modules/nw-metalLB-basic-upgrade-operator.adoc[leveloffset=+1]