.. _envoy_v3_api_file_envoy/extensions/retry/host/omit_host_metadata/v3/omit_host_metadata_config.proto: Omit host metadata retry predicate ================================== .. _envoy_v3_api_msg_extensions.retry.host.omit_host_metadata.v3.OmitHostMetadataConfig: extensions.retry.host.omit_host_metadata.v3.OmitHostMetadataConfig ------------------------------------------------------------------ `[extensions.retry.host.omit_host_metadata.v3.OmitHostMetadataConfig proto] `_ A retry host predicate that can be used to reject a host based on predefined metadata match criteria. .. _extension_envoy.retry_host_predicates.omit_host_metadata: This extension may be referenced by the qualified name *envoy.retry_host_predicates.omit_host_metadata* .. note:: This extension is intended to be robust against untrusted downstream traffic. It assumes that the upstream is trusted. .. code-block:: json { "metadata_match": "{...}" } .. _envoy_v3_api_field_extensions.retry.host.omit_host_metadata.v3.OmitHostMetadataConfig.metadata_match: metadata_match (:ref:`config.core.v3.Metadata `) Retry host predicate metadata match criteria. The hosts in the upstream cluster with matching metadata will be omitted while attempting a retry of a failed request. The metadata should be specified under the *envoy.lb* key.