Question: Header-based TrafficSplit

[ruokun-niu]

Hi SMI,

I was going through your documentation on the v1alpah4 of TrafficSplit and I got a bit confused by the definition.

The screenshot below showcases an A/B test example that configures traffic-splitting based on the headers.

In this example, all Firefox users will be route to website-v2, and "all the others will be routed to the root Kubernetes service". In this case, does the root Kubernetes service refer to the website root service, or another service? In other words, for traffic that does not match with the HTTPRouteGroup in matches, where does it get directed/split to?

Thanks in advance.