Package io.envoyproxy.envoy.service.extension.v3

Class ExtensionConfigDiscoveryServiceGrpc.ExtensionConfigDiscoveryServiceImplBase

java.lang.Object
io.envoyproxy.envoy.service.extension.v3.ExtensionConfigDiscoveryServiceGrpc.ExtensionConfigDiscoveryServiceImplBase
All Implemented Interfaces:
ExtensionConfigDiscoveryServiceGrpc.AsyncService, io.grpc.BindableService
Enclosing class:
ExtensionConfigDiscoveryServiceGrpc
public abstract static class ExtensionConfigDiscoveryServiceGrpc.ExtensionConfigDiscoveryServiceImplBase extends Object implements io.grpc.BindableService, ExtensionConfigDiscoveryServiceGrpc.AsyncService
Base class for the server implementation of the service ExtensionConfigDiscoveryService. 
 A service that supports dynamic configuration updates for a specific filter.
 Currently, ECDS is supported for network filters, HTTP filters, UDP session filters, and listener filters.
 Please check :ref:`Extension Config Discovery Service (ECDS) API <config_overview_extension_discovery>`.
 The overall extension config discovery service works as follows:
 #. A filter (:ref:`Downstream Network <envoy_v3_api_field_config.listener.v3.Filter.config_discovery>`,
    :ref:`Upstream Network <envoy_v3_api_field_config.cluster.v3.Filter.config_discovery>`,
    :ref:`Listener <envoy_v3_api_field_config.listener.v3.ListenerFilter.config_discovery>`,
    :ref:`UDP Session <envoy_v3_api_field_extensions.filters.udp.udp_proxy.v3.UdpProxyConfig.SessionFilter.config_discovery>`,
    or :ref:`HTTP <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpFilter.config_discovery>`)
    contains a (:ref:`ExtensionConfigSource config discovery <envoy_v3_api_msg_config.core.v3.ExtensionConfigSource>`) configuration. This configuration
    includes a :ref:`config_source <envoy_v3_api_field_config.core.v3.ExtensionConfigSource.config_source>`,
    from which the filter configuration will be fetched.
 #. The client then registers for a resource using the filter name as the ``resource_name``.
 #. The xDS server sends back the filter's configuration.
 #. The client stores the configuration that will be used in the next instantiation of the filter chain,
    i.e., for the next requests. Whenever an updated filter configuration arrives, it will be taken into
    account in the following instantiation of the filter chain.
 .. note::
   Filters that are configured using ECDS are warmed. For more details see
   :ref:`ExtensionConfigSource <envoy_v3_api_msg_config.core.v3.ExtensionConfigSource>`.
 Return extension configurations.

  • Constructor Details

    • ExtensionConfigDiscoveryServiceImplBase

      public ExtensionConfigDiscoveryServiceImplBase()

  • Method Details

    • bindService

      public final io.grpc.ServerServiceDefinition bindService()
      Specified by:
      bindService in interface io.grpc.BindableService