2 top-level fields · last changed in Istio 1.24.0
Configuration affecting label/content routing, sni routing, etc. See more details at: https://istio.io/docs/reference/config/networking/virtual-service.html
A list of namespaces to which this virtual service is exported.
The names of gateways and sidecars that should apply these routes.
The destination hosts to which traffic is being sent.
An ordered list of route rules for HTTP traffic.
Cross-Origin Resource Sharing policy (CORS).
Indicates whether the caller is allowed to send the actual request (not the preflight) using credentials.
List of HTTP headers that can be used when requesting the resource.
List of HTTP methods allowed to access the resource.
String patterns that match allowed origins.
[RE2 style regex-based match](https://github.com/google/re2/wiki/Syntax).
A list of HTTP headers that the browsers are allowed to access.
Specifies how long the results of a preflight request can be cached.
Indicates whether preflight requests not matching the configured allowed origin shouldn't be forwarded to the upstream. Valid Options: FORWARD, IGNORE
Delegate is used to specify the particular VirtualService which can be used to define delegate HTTPRoute.
Name specifies the name of the delegate VirtualService.
Namespace specifies the namespace where the delegate VirtualService resides.
A HTTP rule can either return a direct_response, redirect or forward (default) traffic.
Specifies the content of the response body.
response body as base64 encoded bytes.
Specifies the HTTP response status to be returned.
Fault injection policy to apply on HTTP traffic at the client side.
Abort Http request attempts and return error codes back to downstream service, giving the impression that the upstream service is faulty.
GRPC status code to use to abort the request.
HTTP status code to use to abort the Http request.
Percentage of requests to be aborted with the error code provided.
Delay requests before forwarding, emulating various failures such as network issues, overloaded upstream service, etc.
Add a fixed delay before forwarding the request.
Percentage of requests on which the delay will be injected (0-100).
Percentage of requests on which the delay will be injected.
Match conditions to be satisfied for the rule to be activated.
HTTP Authority values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for [RE2 style regex-based match](https://github.com/google/re2/wiki/Syntax).
[RE2 style regex-based match](https://github.com/google/re2/wiki/Syntax).
Names of gateways where the rule should be applied.
The header keys must be lowercase and use hyphen as the separator, e.g.
[RE2 style regex-based match](https://github.com/google/re2/wiki/Syntax).
Flag to specify whether the URI matching should be case-insensitive.
HTTP Method values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for [RE2 style regex-based match](https://github.com/google/re2/wiki/Syntax).
[RE2 style regex-based match](https://github.com/google/re2/wiki/Syntax).
The name assigned to a match.
Specifies the ports on the host that is being addressed.
Query parameters for matching.
[RE2 style regex-based match](https://github.com/google/re2/wiki/Syntax).
URI Scheme values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for [RE2 style regex-based match](https://github.com/google/re2/wiki/Syntax).
[RE2 style regex-based match](https://github.com/google/re2/wiki/Syntax).
One or more labels that constrain the applicability of a rule to source (client) workloads with the given labels.
Source namespace constraining the applicability of a rule to workloads in that namespace.
The human readable prefix to use when emitting statistics for this route.
URI to match values are case-sensitive and formatted as follows: - `exact: "value"` for exact string match - `prefix: "value"` for prefix-based match - `regex: "value"` for [RE2 style regex-based match](https://github.com/google/re2/wiki/Syntax).
[RE2 style regex-based match](https://github.com/google/re2/wiki/Syntax).
withoutHeader has the same syntax with the header, but has opposite meaning.
[RE2 style regex-based match](https://github.com/google/re2/wiki/Syntax).
Mirror HTTP traffic to a another destination in addition to forwarding the requests to the intended destination.
The name of a service from the service registry.
Specifies the port on the host that is being addressed.
The name of a subset within the service.
Percentage of the traffic to be mirrored by the `mirror` field.
Specifies the destinations to mirror HTTP traffic in addition to the original destination.
Destination specifies the target of the mirror operation.
The name of a service from the service registry.
Specifies the port on the host that is being addressed.
The name of a subset within the service.
Percentage of the traffic to be mirrored by the `destination` field.
The name assigned to the route for debugging purposes.
A HTTP rule can either return a direct_response, redirect or forward (default) traffic.
On a redirect, overwrite the Authority/Host portion of the URL with this value.
On a redirect, dynamically set the port: * FROM_PROTOCOL_DEFAULT: automatically set to 80 for HTTP and 443 for HTTPS. Valid Options: FROM_PROTOCOL_DEFAULT, FROM_REQUEST_PORT
On a redirect, overwrite the port portion of the URL with this value.
On a redirect, Specifies the HTTP status code to use in the redirect response.
On a redirect, overwrite the scheme portion of the URL with this value.
On a redirect, overwrite the Path portion of the URL with this value.
Retry policy for HTTP requests.
Number of retries to be allowed for a given request.
Timeout per attempt for a given request, including the initial call and any retries.
Specifies the conditions under which retry takes place.
Flag to specify whether the retries should retry to other localities.
Rewrite HTTP URIs and Authority headers.
rewrite the Authority/Host header with this value.
rewrite the path (or the prefix) portion of the URI with this value.
rewrite the path portion of the URI with the specified regex.
[RE2 style regex-based match](https://github.com/google/re2/wiki/Syntax).
The string that should replace into matching portions of original URI.
A HTTP rule can either return a direct_response, redirect or forward (default) traffic.
Destination uniquely identifies the instances of a service to which the request/connection should be forwarded to.
The name of a service from the service registry.
Specifies the port on the host that is being addressed.
The name of a subset within the service.
Weight specifies the relative proportion of traffic to be forwarded to the destination.
Timeout for HTTP requests, default is disabled.
An ordered list of route rules for opaque TCP traffic.
Match conditions to be satisfied for the rule to be activated.
IPv4 or IPv6 ip addresses of destination with optional subnet.
Names of gateways where the rule should be applied.
Specifies the port on the host that is being addressed.
One or more labels that constrain the applicability of a rule to workloads with the given labels.
Source namespace constraining the applicability of a rule to workloads in that namespace.
The destination to which the connection should be forwarded to.
Destination uniquely identifies the instances of a service to which the request/connection should be forwarded to.
The name of a service from the service registry.
Specifies the port on the host that is being addressed.
The name of a subset within the service.
Weight specifies the relative proportion of traffic to be forwarded to the destination.
An ordered list of route rule for non-terminated TLS & HTTPS traffic.
Match conditions to be satisfied for the rule to be activated.
IPv4 or IPv6 ip addresses of destination with optional subnet.
Names of gateways where the rule should be applied.
Specifies the port on the host that is being addressed.
SNI (server name indicator) to match on.
One or more labels that constrain the applicability of a rule to workloads with the given labels.
Source namespace constraining the applicability of a rule to workloads in that namespace.
The destination to which the connection should be forwarded to.
Destination uniquely identifies the instances of a service to which the request/connection should be forwarded to.
The name of a service from the service registry.
Specifies the port on the host that is being addressed.
The name of a subset within the service.
Weight specifies the relative proportion of traffic to be forwarded to the destination.
Current service state of the resource.
Last time we probed the condition.
Last time the condition transitioned from one status to another.
Human-readable message indicating details about last transition.
Unique, one-word, CamelCase reason for the condition's last transition.
Status is the status of the condition.
Type is the type of the condition.
Resource Generation to which the Reconciled Condition refers.
Includes any errors or warnings detected by Istio's analyzers.
A url pointing to the Istio documentation for this specific error type.
Represents how severe a message is. Valid Options: UNKNOWN, ERROR, WARNING, INFO
A 7 character code matching `^IST[0-9]{4}$` intended to uniquely identify the message type.
A human-readable name for the message type.
Source: crd-all.gen.yaml
Changes to VirtualService (networking.istio.io/v1) in each Istio version, compared to the version before it.
3 properties have been added
Released · View VirtualService in 1.24.0
1 property has been added
13 properties have changed the description
Released · View VirtualService in 1.23.0
VirtualService was first seen on this version of Istio
Released · View VirtualService in 1.22.0
No examples of VirtualService yet. Contribute one on GitHub.
kubespec.dev