Extension configuration

    In case the control plane lacks the schema definitions for an extension, udpa.type.v1.TypedStruct should be used as a generic container. The type URL inside it is then used by a client to convert the contents to a typed configuration resource. For example, the above example could be written as follows:

    2. typed_config:
    3.   "@type": type.googleapis.com/udpa.type.v1.TypedStruct
    4.   type_url: type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
    5.   value:
    7.     rds:
    8.       route_config_name: local_route
    9.       config_source:
    10.         api_config_source:
    11.           api_type: GRPC
    12.             envoy_grpc:
    13.               cluster_name: xds_cluster
    14.     http_filters:
    15.     - name: front-router
    16.       typed_config:

    Extension configuration can be supplied dynamically from an xDS management server using . The name field in the extension configuration acts as the resource identifier. For example, HTTP connection manager supports dynamic filter re-configuration for HTTP filters.

    Extension config discovery service has a tree rooted at <stat_prefix>.extension_config_discovery.<extension_config_name>. In addition to the common subscription statistics, it also provides the following: