feat: Add VirtualServerRoute Label Selectors to NIC

content/nic/configuration/virtualserver-and-virtualserverroute-resources.md

@@ -54,8 +54,14 @@ spec:
   - path: =/green/tea
     action:
       pass: tea
+  - path: /dynamic
+    routeSelector:
+      matchLabels:
+        app: cafe
 ```
 
+The example above shows a VirtualServer with both traditional static routes and a dynamic route using `routeSelector`. The route with path `/dynamic` will automatically include any VirtualServerRoute resources that have the label `app: cafe`.
+
 |Field | Description | Type | Required |
 | ---| ---| ---| --- |
 |``host`` | The host (domain name) of the server. Must be a valid subdomain as defined in RFC 1123, such as ``my-app`` or ``hello.example.com``. When using a wildcard domain like ``*.example.com`` the domain must be contained in double quotes. The ``host`` value needs to be unique among all Ingress and VirtualServer resources. See also [Handling Host and Listener Collisions]({{< ref "/nic/configuration/host-and-listener-collisions.md" >}}). | ``string`` | Yes |
@@ -205,17 +211,31 @@ The route defines rules for matching client requests to actions like passing a r
 |``splits`` | The default splits configuration for traffic splitting. Must include at least 2 splits. | [[]split](#split) | No |
 |``matches`` | The matching rules for advanced content-based routing. Requires the default ``action`` or ``splits``.  Unmatched requests will be handled by the default ``action`` or ``splits``. | [matches](#match) | No |
 |``route`` | The name of a VirtualServerRoute resource that defines this route. If the VirtualServerRoute belongs to a different namespace than the VirtualServer, you need to include the namespace. For example, ``tea-namespace/tea``. | ``string`` | No |
+|``routeSelector`` | The RouteSelector allows selecting VirtualServerRoute resources using label selectors instead of specifying them by name and namespace. | [routeSelector](#virtualserverrouterouteselector) | No |
 |``errorPages`` | The custom responses for error codes. NGINX will use those responses instead of returning the error responses from the upstream servers or the default responses generated by NGINX. A custom response can be a redirect or a canned response. For example, a redirect to another URL if an upstream server responded with a 404 status code. | [[]errorPage](#errorpage) | No |
 |``location-snippets`` | Sets a custom snippet in the location context. Overrides the ``location-snippets`` ConfigMap key. | ``string`` | No |
 {{< /table >}}
 
-\* -- a route must include exactly one of the following: `action`, `splits`, or `route`.
+\* -- a route must include exactly one of the following: `action`, `splits`, `route` or `routeSelector`
+
+### VirtualServer.Route.RouteSelector
+
+The RouteSelector field allows you to dynamically select VirtualServerRoute resources using label selectors instead of specifying them by name and namespace. This provides a more flexible and scalable way to associate VirtualServerRoutes with a VirtualServer route.
+
+See the [VirtualServerRoute specification](#virtualserverroute-specification) section below for examples of how to use RouteSelector with VirtualServerRoute resources.
+
+|Field | Description | Type | Required |
+| ---| ---| ---| --- |
+|``matchLabels`` | A map of key-value pairs. Each key-value pair in the matchLabels map is equivalent to an element of matchExpressions, whose key field is "key", the operator is "In", and the values array contains only "value". The requirements are ANDed. | ``map[string]string`` | Yes |
+|``matchExpressions`` | A list of label selector requirements. The requirements are ANDed. For more information on label selector requirements, see the [Kubernetes documentation](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#resources-that-support-set-based-requirements). | N/A | No |
 
 ## VirtualServerRoute specification
 
 The VirtualServerRoute resource defines a route for a VirtualServer. It can consist of one or multiple subroutes. The VirtualServerRoute is an alternative to [Mergeable Ingress types]({{< ref "/nic/configuration/ingress-resources/cross-namespace-configuration.md" >}}).
 
-In the example below, the VirtualServer `cafe` from the namespace `cafe-ns` defines a route with the path `/coffee`, which is further defined in the VirtualServerRoute `coffee` from the namespace `coffee-ns`.
+VirtualServer routes can reference VirtualServerRoute resources in two ways: by name using the `route` field, or dynamically using the `routeSelector` field with label selectors. The `routeSelector` approach allows you to add new VirtualServerRoute resources without modifying the VirtualServer configuration.
+
+In the example below, the VirtualServer `cafe` from the namespace `cafe-ns` defines routes using both approaches: the `/coffee` path references a specific VirtualServerRoute by name, while the `/decaf` path uses `routeSelector` to dynamically select any VirtualServerRoute with the label `app: cafe`.
 
 VirtualServer:
 
@@ -237,6 +257,10 @@ spec:
       pass: tea
   - path: /coffee
     route: coffee-ns/coffee
+  - path: /decaf
+    routeSelector:
+      matchLabels:
+        app: cafe
 ```
 
 VirtualServerRoute:
@@ -247,6 +271,8 @@ kind: VirtualServerRoute
 metadata:
   name: coffee
   namespace: coffee-ns
+  labels:
+    app: cafe
 spec:
   host: cafe.example.com
   upstreams:
@@ -274,6 +300,7 @@ Note that each subroute must have a `path` that starts with the same prefix (her
 |``subroutes`` | A list of subroutes. | [[]subroute](#virtualserverroutesubroute) | No |
 |``ingressClassName`` | Specifies which Ingress Controller must handle the VirtualServerRoute resource. Must be the same as the ``ingressClassName`` of the VirtualServer that references this resource. | ``string``_ | No |
 
+
 ### VirtualServerRoute.Subroute
 
 The subroute defines rules for matching client requests to actions like passing a request to an upstream. For example: