Fix incorrect virtualservice to gateway assignment faq guidance
@@ -142,7 +142,7 @@ If you create a VirtualService and assign it TLS/SSL configuration, it will be b
In the event you have multiple Gateways/listeners or you want more fine-grained control over how a VirtualService gets associated with a Gateway, you can explicitly add the VirtualService name to the Gateway resource like this:
-{{< highlight yaml "hl_lines=9-11" >}}
+{{< highlight yaml "hl_lines=9-12" >}}
apiVersion: gateway.solo.io/v1
kind: Gateway
metadata:
@@ -151,6 +151,7 @@ metadata:
spec:
bindAddress: '::'
bindPort: 8080
+ httpGateway:
virtualServices:
- name: pet-virtual-service
namespace: gloo-system
@@ -163,6 +164,25 @@ status:
state: 1
{{< /highlight >}}
+Or you can match on a map of labels that you have applied to the VirtualService:
+
+{{< highlight yaml "hl_lines=9-12" >}}
+apiVersion: gateway.solo.io/v1
+kind: Gateway
+metadata:
+ name: gateway-proxy
+ namespace: gloo-system
+spec:
+ bindAddress: '::'
+ bindPort: 8080
+ httpGateway:
+ virtualServiceSelector:
+ label-name: label-value
+ anotherlabel-name: anotherlabel-value
+{{< /highlight >}}
+
+
+
#### How do I configure TLS for Gloo
Gloo can be configured with TLS and SNI for multiple virtual hosts. Please [see the documentation for how to do that]({{< versioned_link_path fromRoot="/guides/security/tls/server_tls/">}})
