Add Kuryr docs about limitation of service without selector (#28022)

When using services without selectors with Kuryr and OVN octavia
provider the Endpoints address should be either on the Nodes or Pods
subnet. This commit includes this restriction to the docs.

Co-authored-by: Max Bridges <[email protected]>

Author: MaysaMacedo

modules/installation-osp-kuryr-known-limitations.adoc

@@ -11,11 +11,13 @@ Using {product-title} with Kuryr SDN has several known limitations.
 [id="openstack-general-limitations_{context}"]
 == {rh-openstack} general limitations
 
-{product-title} with Kuryr SDN does not support `Service` objects with type `NodePort`.
+Using {product-title} with Kuryr SDN has several limitations that apply to all versions and environments:
 
-If the machines subnet is not connected to a router, or if the
-subnet is connected, but the router has no external gateway set,
-Kuryr cannot create floating IPs for `Service` objects with type `LoadBalancer`.
+* `Service` objects with the `NodePort` type are not supported.
+
+* Clusters that use the OVN Octavia provider driver support `Service` objects for which the `.spec.selector` property is unspecified only if the `.subsets.addresses` property of the `Endpoints` object includes the subnet of the nodes or pods. 
+
+* If the subnet on which machines are created is not connected to a router, or if the subnet is connected, but the router has no external gateway set, Kuryr cannot create floating IPs for `Service` objects with type `LoadBalancer`.
 
 [discrete]
 [id="openstack-version-limitations_{context}"]