On-demand VHDS, S/RDS and CDS Updates
The on demand filter can be used to support either on demand VHDS or S/RDS update together with on demand CDS update if configured in the filter chain.
The on-demand update filter can be used to request a virtual host data if it’s not already present in the Route Configuration. The contents of the Host or :authority header is used to create the on-demand request. For an on-demand request to be created, VHDS must be enabled and either Host or :authority header be present.
The on-demand update filter can also be used to request a Route Configuration data if RouteConfiguration is specified to be loaded on demand in the Scoped RouteConfiguration. The contents of the HTTP header is used to find the scope and create the on-demand request.
The on-demand update filter can also be used to request a cluster when the target cluster name is only known after receiving a request and the cluster is missing - this is a scenario that could happen with the cluster_header route action. For an on demand request to be created, odcds (or its per route counterpart) must be specified and a header specified in cluster_header action must be present in the HTTP request.
On-demand VHDS and on-demand S/RDS can not be used at the same time at this point.
On-demand CDS can also be enabled or disabled per virtual host or route. Specifying an extension config in virtual host’s typed_per_filter_config or the route’s typed_per_filter_config without the odcds field disables the on demand CDS for requests using this virtual host or route. Conversely, if odcds is specified, on demand CDS is enabled for requests using this virtual host or route.
This filter should be configured with the type URL
The filter should be placed before envoy.filters.http.router filter in the HttpConnectionManager’s filter chain.