Virtual Services

Virtual Services define a “virtual API” that gets exposed to clients along with a set of routing rules to backend upstream services/functions. You can also specify TLS/SNI configuration at this level to present certificates to callers and even require certificates from clients (mutual TLS). See the Virtual Service section in the concepts documentation for more background.

The sections in Virtual Services are listed below for reference. If you are new to Virtual Services we recommend starting with the Hello World example and then trying out different matching rules starting with Path Matching.

If you need a solution that splits up parts of the query path such that different application teams can manage routes for different query paths, take a look that the Delegation with Route Tables documentation. Route tables allow you to have global visibility over all route rules while granting fine-grained edit rights to specific roles/teams.