Merge pull request #53075 from sjhala-ccs/cnv-18350

CNV-18350: Adding info about load balancing with MetalLB

Author: sjhala-ccs

modules/virt-about-services.adoc

@@ -13,24 +13,8 @@ ClusterIP:: Exposes the service on an internal IP address within the cluster. `C
 NodePort:: Exposes the service on the same port of each selected node in the cluster. `NodePort` makes a service accessible from outside the cluster.
 
 LoadBalancer:: Creates an external load balancer in the current cloud (if supported) and assigns a fixed, external IP address to the service.
-
-
-[id="services-dual-stack-cluster_{context}"]
-== Dual-stack support
-
-If IPv4 and IPv6 dual-stack networking is enabled for your cluster, you can create a service that uses IPv4, IPv6, or both, by defining the `spec.ipFamilyPolicy` and the `spec.ipFamilies` fields in the `Service` object.
-
-The `spec.ipFamilyPolicy` field can be set to one of the following values:
-
-SingleStack:: The control plane assigns a cluster IP address for the service based on the first configured service cluster IP range.
-
-PreferDualStack:: The control plane assigns both IPv4 and IPv6 cluster IP addresses for the service on clusters that have dual-stack configured.
-
-RequireDualStack:: This option fails for clusters that do not have dual-stack networking enabled. For clusters that have dual-stack configured, the behavior is the same as when the value is set to `PreferDualStack`. The control plane allocates cluster IP addresses from both IPv4 and IPv6 address ranges.
-
-You can define which IP family to use for single-stack or define the order of IP families for dual-stack by setting the `spec.ipFamilies` field to one of the following array values:
-
-* `[IPv4]`
-* `[IPv6]`
-* `[IPv4, IPv6]`
-* `[IPv6, IPv4]`
++
+[NOTE]
+====
+For on-premise clusters, you can configure a load balancing service by using the MetalLB Operator in layer 2 mode. The BGP mode is not supported. The MetalLB Operator is installed in the `metallb-system` namespace.
+====

modules/virt-dual-stack-support-services.adoc

@@ -0,0 +1,25 @@
+// Module included in the following assemblies:
+//
+// * virt/virtual_machines/vm_networking/virt-creating-service-vm.adoc
+
+
+:_content-type: REFERENCE
+[id="virt-dual-stack-support-services_{context}"]
+== Dual-stack support
+
+If IPv4 and IPv6 dual-stack networking is enabled for your cluster, you can create a service that uses IPv4, IPv6, or both, by defining the `spec.ipFamilyPolicy` and the `spec.ipFamilies` fields in the `Service` object.
+
+The `spec.ipFamilyPolicy` field can be set to one of the following values:
+
+SingleStack:: The control plane assigns a cluster IP address for the service based on the first configured service cluster IP range.
+
+PreferDualStack:: The control plane assigns both IPv4 and IPv6 cluster IP addresses for the service on clusters that have dual-stack configured.
+
+RequireDualStack:: This option fails for clusters that do not have dual-stack networking enabled. For clusters that have dual-stack configured, the behavior is the same as when the value is set to `PreferDualStack`. The control plane allocates cluster IP addresses from both IPv4 and IPv6 address ranges.
+
+You can define which IP family to use for single-stack or define the order of IP families for dual-stack by setting the `spec.ipFamilies` field to one of the following array values:
+
+* `[IPv4]`
+* `[IPv6]`
+* `[IPv4, IPv6]`
+* `[IPv6, IPv4]`

virt/virtual_machines/vm_networking/virt-creating-service-vm.adoc

@@ -10,6 +10,13 @@ You can expose a virtual machine within the cluster or outside the cluster by us
 
 include::modules/virt-about-services.adoc[leveloffset=+1]
 
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../networking/metallb/metallb-operator-install.adoc#metallb-operator-install[Installing the MetalLB Operator]
+* xref:../../../networking/metallb/metallb-configure-services.adoc#metallb-configure-services[Configuring services to use MetalLB]
+
+include::modules/virt-dual-stack-support-services.adoc[leveloffset=+1]
+
 include::modules/virt-creating-a-service-from-a-virtual-machine.adoc[leveloffset=+1]
 
 [role="_additional-resources"]