diff --git a/content/en/docs/reference/config/networking/destination-rule/index.html b/content/en/docs/reference/config/networking/destination-rule/index.html index 7ec9ac9897a5..fd742e34f205 100644 --- a/content/en/docs/reference/config/networking/destination-rule/index.html +++ b/content/en/docs/reference/config/networking/destination-rule/index.html @@ -1411,6 +1411,15 @@

LoadBalancerSettings.ConsistentHa properties. The affinity to a particular destination host may be lost when one or more hosts are added/removed from the destination service.

+

Note: consistent hashing is less reliable at maintaining affinity than common +“sticky sessions” implementations, which often encode a specific destination in +a cookie, ensuring affinity is maintained as long as the backend remains. +With consistent hash, the guarantees are weaker; any host addition or removal can +break affinity for 1/backends requests.

+

Warning: consistent hashing depends on each proxy having a consistent view of endpoints. +This is not the case when locality load balancing is enabled. Locality load balancing +and consistent hash will only work together when all proxies are in the same locality, +or a high level load balancer handles locality affinity.

diff --git a/content/en/docs/reference/config/proxy_extensions/accesslogpolicy/index.html b/content/en/docs/reference/config/proxy_extensions/accesslogpolicy/index.html index 291d833a7383..4021f77eb334 100644 --- a/content/en/docs/reference/config/proxy_extensions/accesslogpolicy/index.html +++ b/content/en/docs/reference/config/proxy_extensions/accesslogpolicy/index.html @@ -10,14 +10,16 @@ number_of_entries: 1 ---

Accesslog Policy plugin is a stateful http log sampler. -It decides whether a request is logged based on the following rules. - 1. All requests resulting in errors are logged. - 2. First successful request within logwindowduration from a specific - source ip (source principal) is logged. -The plugin records its decision in the istio.accesslogpolicy attribute with +It decides whether a request is logged based on the following rules.

+
    +
  1. All requests resulting in errors are logged.
    2. +
  2. First successful request within log_window_duration from a specific +source ip (source principal) is logged. +The plugin records its decision in the istio.access_log_policy attribute with a value of “no”. A downstream plugin may honor the the attribute. For example, Stackdriver plugin will not produce an access log entry if this -attribute is set.

    +attribute is set.
    3. +

AccessLogPolicyConfig

diff --git a/content/en/docs/reference/config/proxy_extensions/attributegen/index.html b/content/en/docs/reference/config/proxy_extensions/attributegen/index.html index de64804a172c..3e1250e37d8d 100644 --- a/content/en/docs/reference/config/proxy_extensions/attributegen/index.html +++ b/content/en/docs/reference/config/proxy_extensions/attributegen/index.html @@ -10,15 +10,13 @@ weight: 20 number_of_entries: 3 --- -

AttributeGen plugin uses builtin attributes +

AttributeGen plugin uses builtin +attributes as inputs and produces new attributes that can be used by downstream plugins.

-

The following is an example of a configuration that produces one attribute named istio_operationId using request.url_path and request.method.

-

{{}} {{}}

- 
{
   "attributes": [
     {
@@ -46,20 +44,15 @@
 }
-

{{}} {{}}

-

If the Stats plugin runs after AttributeGen, it can use istio_operationId to populate a dimension on a metric.

-

The following is an example of response codes being mapped into a smaller number of response classes as the istio_responseClass attribute. For example, all response codes in 200s are mapped to 2xx.

-

{{}} {{}}

- 
{
   "attributes": [
     {
@@ -99,11 +92,9 @@
 }
-

{{}} {{}}

- -

If multiple AttributeGene configurations produce the same attribute, the +

If multiple AttributeGen configurations produce the same attribute, the result of the last configuration will be visible to downstream filters.

PluginConfig

@@ -168,22 +159,17 @@

AttributeGeneration

The name of the attribute that is populated on a successful match. An attribute name SHOULD NOT contain a .. You may use underscores for namespacing instead.

-

Example: istio_operationId

-

istio_ attribute namespace is reserved by Istio.

-

AttributeGeneration may fail to evaluate when an attribute is not available. For example, response.code may not be available when a request ends abruptly. When attribute generation fails, it will not populate the attribute.

-

If the generated attribute is used by an authz plugin, it should account for the possibility that the attribute may be missing. Use has(attribute_name) function to check for presence of an attribute before using its value, and provide appropriate defaults. For example the following is a safe use of response.code

-

has(response.code)?response.code:200

@@ -228,13 +214,11 @@

Match

+ + + + + + + + + +

The condition is a CEL expression -that may use builtin attributes.

- +that may use builtin +attributes.

Example:

-

{{}} {{}}

- 
   {
      "value": "GetBook",
      "condition":
@@ -242,23 +226,17 @@ 
Match

      && request.method == 'GET'"
    },
-

Note: CEL uses re2 regex library. Use anchors {^, $} to ensure that the regex evaluates efficiently.

-

Note: request.url_path is normalized and stripped of query params.

-

a Read only operation on books

- 
{ "value": "ReadOnlyBooks",
   "condition": "request.url_path.startsWith('/books/') &&
   in(request.method, ['GET', 'HEAD'])"}
-

{{}} {{}}

-

An empty condition evaluates to true and should be used to provide a default value.

diff --git a/content/en/docs/reference/config/proxy_extensions/metadata_exchange/index.html b/content/en/docs/reference/config/proxy_extensions/metadata_exchange/index.html index a24f77948936..cc78bf7992b3 100644 --- a/content/en/docs/reference/config/proxy_extensions/metadata_exchange/index.html +++ b/content/en/docs/reference/config/proxy_extensions/metadata_exchange/index.html @@ -40,7 +40,6 @@

PluginConfig

google.protobuf.UInt32Value

Wrapper message for uint32.

-

The JSON representation for UInt32Value is JSON number.

diff --git a/content/en/docs/reference/config/proxy_extensions/stackdriver/index.html b/content/en/docs/reference/config/proxy_extensions/stackdriver/index.html index fc15e7ac6b01..f507adcac6c7 100644 --- a/content/en/docs/reference/config/proxy_extensions/stackdriver/index.html +++ b/content/en/docs/reference/config/proxy_extensions/stackdriver/index.html @@ -7,12 +7,12 @@ layout: protoc-gen-docs generator: protoc-gen-docs weight: 20 -number_of_entries: 3 +number_of_entries: 4 ---

CustomConfig

Custom instance configuration overrides. -Provides a way to customize metrics/logs.

+Provides a way to customize logs.

@@ -42,7 +42,7 @@

CustomConfig

PluginConfig

-

next id: 15

+

next id: 17

@@ -100,35 +100,6 @@

PluginConfig

productpage.default.svc.cluster.local. If not provided, request host header will be used instead

- - - - - - - - - - - - - - - - - - - + + + + + + @@ -232,6 +205,19 @@

PluginConfig

series will never be expired. This option is useful to avoid unbounded metric label explodes proxy memory.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
-No -
enable_mesh_edges_reportingbool -

Optional. Controls whether or not to export mesh edges to a mesh edges -service. This is disabled by default.

- -		 -No -
mesh_edges_reporting_durationDuration -

Optional. Allows configuration of the time between calls out to the mesh -edges service to report NEW edges. The minimum configurable duration is -10s. NOTE: This option ONLY configures the intermediate reporting of -novel edges. Once every 10m, all edges observed in that 10m window are -reported and the local cache is cleared. -The default duration is 1m. Any value greater than 10m will result in -reporting every 10m.

- 		No @@ -167,19 +138,6 @@

PluginConfig

Optional. Allows configuration of the number of traffic assertions to batch into a single request. Default is 100. Max is 1000.

-		 -No -
disable_http_size_metricsbool -

Optional. Allows disabling of reporting of the request and response size -metrics for HTTP traffic. Defaults to false (request and response size -metrics are enabled).

- 		No @@ -200,7 +158,21 @@

PluginConfig

access_logging AccessLogging -

Optional. Controls what type of logs to export..

+

Optional. Controls what type of logs to export.

+ +		 +No +
access_logging_filter_expressionstring +

CEL expression for filtering access logging. If the expression evaluates +to true, an access log entry will be generated. Otherwise, no access log +entry will be generated. +NOTE: Audit logs ignore configured filters.

 @@ -214,7 +186,8 @@

PluginConfig

(Optional) Collection of tag names and tag expressions to include in the logs. Conflicts are resolved by the tag name by overriding previously supplied values. Does not apply to audit logs. -See https://istio.io/latest/docs/tasks/observability/metrics/customize-metrics/#use-expressions-for-values +See +https://istio.io/latest/docs/tasks/observability/metrics/customize-metrics/#use-expressions-for-values for more details about the expression language.

 +No +
metrics_overridesmap<string, MetricsOverride> +

Optional. Allows altering metrics behavior. +Metric names for specifying overloads drop the istio.io/service prefix. +Examples: server/request_count, client/roundtrip_latencies

+ 		No @@ -244,6 +230,96 @@

PluginConfig

Optional. Controls whether to export server access log. This is deprecated in favor of AccessLogging enum.

+		 +No +
enable_mesh_edges_reportingbool +

Optional. Controls whether or not to export mesh edges to a mesh edges +service. This is disabled by default. +Deprecated – Mesh edge reporting is no longer supported and this setting +is no-op.

+ +		 +No +
mesh_edges_reporting_durationDuration +

Optional. Allows configuration of the time between calls out to the mesh +edges service to report NEW edges. The minimum configurable duration is +10s. NOTE: This option ONLY configures the intermediate reporting of +novel edges. Once every 10m, all edges observed in that 10m window are +reported and the local cache is cleared. +The default duration is 1m. Any value greater than 10m will result in +reporting every 10m. +Deprecated – Mesh edge reporting is no longer supported and this setting +is no-op.

+ +		 +No +
disable_http_size_metricsbool +

Optional. Allows disabling of reporting of the request and response size +metrics for HTTP traffic. Defaults to false (request and response size +metrics are enabled). +Deprecated – use metrics_overrides instead. +if metrics_overrides is used, this value will be ignored.

+ +		 +No +
+
+

MetricsOverride

+
+

Provides behavior modifications for Cloud Monitoring metrics.

+ + + + + + + + + + + + + + + + + + + + + diff --git a/content/en/docs/reference/config/proxy_extensions/stats/index.html b/content/en/docs/reference/config/proxy_extensions/stats/index.html index 37dbb855e658..5acd5cf8108e 100644 --- a/content/en/docs/reference/config/proxy_extensions/stats/index.html +++ b/content/en/docs/reference/config/proxy_extensions/stats/index.html @@ -7,7 +7,7 @@ layout: protoc-gen-docs generator: protoc-gen-docs weight: 20 -number_of_entries: 4 +number_of_entries: 5 ---

MetricConfig

@@ -70,6 +70,18 @@

MetricConfig

+ + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -245,6 +192,17 @@

PluginConfig

+ + + + + +
FieldTypeDescriptionRequired
dropbool +

Optional. If true, no data for the associated metric will be collected or +exported.

+ +		 +No +
tag_overridesmap<string, string> +

Optional. Maps tag names to value expressions that will be used at +reporting time. If the tag name does not match a well-known tag for the +istio Cloud Monitoring metrics, the configuration will have no effect.

+ 		No @@ -282,8 +358,7 @@

PluginConfig.AccessLogging

ERRORS_ONLY

All error logs. This is currently only available for outbound/client side -logs. A request is classified as error when status>=400 or -response_flag != "-"

+logs. A request is classified as error when status>=400 or response_flag != "-"

NOT IMPLEMENTED. (Optional) Conditional enabling the override.

+		 +No +
dropbool +

(Optional) If this is set to true, the metric(s) selected by this +configuration will not be generated or reported.

+ 		No @@ -138,71 +150,6 @@

PluginConfig

debugbool -

next id: 7 -The following settings should be rarely used. -Enable debug for this filter. -DEPRECATED.

- -		 -No -
max_peer_cache_sizeint32 -

maximum size of the peer metadata cache. -A long lived proxy that connects with many transient peers can build up a -large cache. To turn off the cache, set this field to a negative value. -DEPRECATED.

- -		 -No -
stat_prefixstring -

prefix to add to stats emitted by the plugin. -DEPRECATED.

- -		 -No -
field_separatorstring -

Stats api squashes dimensions in a single string. -The squashed string is parsed at prometheus scrape time to recover -dimensions. The following 2 fields set the field and value separators {key: -value} –> key{valueseparator}value{fieldseparator}

- -		 -No -
value_separatorstring -

default: “==”

- -		 -No -
disable_host_header_fallback bool

Metric definitions.

+		 +No +
reporterReporter +

Proxy deployment type.

+ 		No @@ -281,3 +239,33 @@

MetricType
+

Reporter

+
+

Specifies the proxy deployment type.

+ + + + + + + + + + + + + + + + + + +
NameDescription
UNSPECIFIED +

Default value is inferred from the listener direction, as either client or +server sidecar.

+ +
SERVER_GATEWAY +

Shared server gateway, e.g. “waypoint”.

+ +
+
diff --git a/content/en/docs/reference/config/proxy_extensions/wasm-plugin/index.html b/content/en/docs/reference/config/proxy_extensions/wasm-plugin/index.html index 83df4a0cd533..b8fe631b13d8 100644 --- a/content/en/docs/reference/config/proxy_extensions/wasm-plugin/index.html +++ b/content/en/docs/reference/config/proxy_extensions/wasm-plugin/index.html @@ -8,7 +8,7 @@ generator: protoc-gen-docs schema: istio.extensions.v1alpha1.WasmPlugin aliases: [/docs/reference/config/extensions/v1alpha1/wasm-plugin] -number_of_entries: 6 +number_of_entries: 7 ---

WasmPlugins provides a mechanism to extend the functionality provided by the Istio proxy through WebAssembly filters.

@@ -318,6 +318,19 @@

WasmPlugin

Configuration for a Wasm VM. more details can be found here.

+		 +No +
matchTrafficSelector[] +

Specifies the criteria to determine which traffic is passed to WasmPlugin. +If a traffic satisfies any of TrafficSelectors, +the traffic passes the WasmPlugin.

+ 		No @@ -400,6 +413,57 @@

EnvVar

Note that if value_from is HOST, it will be ignored. Defaults to “”.

+		 +No +
+ +

WasmPlugin.TrafficSelector

+
+

TrafficSelector provides a mechanism to select a specific traffic flow +for which this Wasm Plugin will be enabled. +When all the sub conditions in the TrafficSelector are satisfied, the +traffic will be selected.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescriptionRequired
modeWorkloadMode +

Criteria for selecting traffic by their direction. +Note that CLIENT and SERVER are analogous to INBOUND and OUTBOUND, +respectively. +For the gateway, the field should be CLIENT or CLIENT_AND_SERVER. +If not specified, the default value is CLIENT_AND_SERVER.

+ +		 +No +
portsPortSelector[] +

Criteria for selecting traffic by their destination port. +More specifically, for the outbound traffic, the destination port would be +the port of the target service. On the other hand, for the inbound traffic, +the destiation port is the port bound by the server process in the same Pod.

+

If one of the given ports is matched, this condition is evaluated to true. +If not specified, this condition is evaluated to true for any port.

+ 		No diff --git a/content/zh/docs/reference/config/networking/destination-rule/index.html b/content/zh/docs/reference/config/networking/destination-rule/index.html index cb80ab3535f3..cbcc1369e613 100644 --- a/content/zh/docs/reference/config/networking/destination-rule/index.html +++ b/content/zh/docs/reference/config/networking/destination-rule/index.html @@ -1411,6 +1411,15 @@

LoadBalancerSettings.ConsistentHa properties. The affinity to a particular destination host may be lost when one or more hosts are added/removed from the destination service.

+

Note: consistent hashing is less reliable at maintaining affinity than common +“sticky sessions” implementations, which often encode a specific destination in +a cookie, ensuring affinity is maintained as long as the backend remains. +With consistent hash, the guarantees are weaker; any host addition or removal can +break affinity for 1/backends requests.

+

Warning: consistent hashing depends on each proxy having a consistent view of endpoints. +This is not the case when locality load balancing is enabled. Locality load balancing +and consistent hash will only work together when all proxies are in the same locality, +or a high level load balancer handles locality affinity.

diff --git a/content/zh/docs/reference/config/proxy_extensions/accesslogpolicy/index.html b/content/zh/docs/reference/config/proxy_extensions/accesslogpolicy/index.html index 291d833a7383..4021f77eb334 100644 --- a/content/zh/docs/reference/config/proxy_extensions/accesslogpolicy/index.html +++ b/content/zh/docs/reference/config/proxy_extensions/accesslogpolicy/index.html @@ -10,14 +10,16 @@ number_of_entries: 1 ---

Accesslog Policy plugin is a stateful http log sampler. -It decides whether a request is logged based on the following rules. - 1. All requests resulting in errors are logged. - 2. First successful request within logwindowduration from a specific - source ip (source principal) is logged. -The plugin records its decision in the istio.accesslogpolicy attribute with +It decides whether a request is logged based on the following rules.

+
    +
  1. All requests resulting in errors are logged.
    2. +
  2. First successful request within log_window_duration from a specific +source ip (source principal) is logged. +The plugin records its decision in the istio.access_log_policy attribute with a value of “no”. A downstream plugin may honor the the attribute. For example, Stackdriver plugin will not produce an access log entry if this -attribute is set.

    +attribute is set.
    3. +

AccessLogPolicyConfig

diff --git a/content/zh/docs/reference/config/proxy_extensions/attributegen/index.html b/content/zh/docs/reference/config/proxy_extensions/attributegen/index.html index de64804a172c..3e1250e37d8d 100644 --- a/content/zh/docs/reference/config/proxy_extensions/attributegen/index.html +++ b/content/zh/docs/reference/config/proxy_extensions/attributegen/index.html @@ -10,15 +10,13 @@ weight: 20 number_of_entries: 3 --- -

AttributeGen plugin uses builtin attributes +

AttributeGen plugin uses builtin +attributes as inputs and produces new attributes that can be used by downstream plugins.

-

The following is an example of a configuration that produces one attribute named istio_operationId using request.url_path and request.method.

-

{{}} {{}}

- 
{
   "attributes": [
     {
@@ -46,20 +44,15 @@
 }
-

{{}} {{}}

-

If the Stats plugin runs after AttributeGen, it can use istio_operationId to populate a dimension on a metric.

-

The following is an example of response codes being mapped into a smaller number of response classes as the istio_responseClass attribute. For example, all response codes in 200s are mapped to 2xx.

-

{{}} {{}}

- 
{
   "attributes": [
     {
@@ -99,11 +92,9 @@
 }
-

{{}} {{}}

- -

If multiple AttributeGene configurations produce the same attribute, the +

If multiple AttributeGen configurations produce the same attribute, the result of the last configuration will be visible to downstream filters.

PluginConfig

@@ -168,22 +159,17 @@

AttributeGeneration

The name of the attribute that is populated on a successful match. An attribute name SHOULD NOT contain a .. You may use underscores for namespacing instead.

-

Example: istio_operationId

-

istio_ attribute namespace is reserved by Istio.

-

AttributeGeneration may fail to evaluate when an attribute is not available. For example, response.code may not be available when a request ends abruptly. When attribute generation fails, it will not populate the attribute.

-

If the generated attribute is used by an authz plugin, it should account for the possibility that the attribute may be missing. Use has(attribute_name) function to check for presence of an attribute before using its value, and provide appropriate defaults. For example the following is a safe use of response.code

-

has(response.code)?response.code:200

@@ -228,13 +214,11 @@

Match

+ + + + + + + + + +

The condition is a CEL expression -that may use builtin attributes.

- +that may use builtin +attributes.

Example:

-

{{}} {{}}

- 
   {
      "value": "GetBook",
      "condition":
@@ -242,23 +226,17 @@ 
Match

      && request.method == 'GET'"
    },
-

Note: CEL uses re2 regex library. Use anchors {^, $} to ensure that the regex evaluates efficiently.

-

Note: request.url_path is normalized and stripped of query params.

-

a Read only operation on books

- 
{ "value": "ReadOnlyBooks",
   "condition": "request.url_path.startsWith('/books/') &&
   in(request.method, ['GET', 'HEAD'])"}
-

{{}} {{}}

-

An empty condition evaluates to true and should be used to provide a default value.

diff --git a/content/zh/docs/reference/config/proxy_extensions/metadata_exchange/index.html b/content/zh/docs/reference/config/proxy_extensions/metadata_exchange/index.html index a24f77948936..cc78bf7992b3 100644 --- a/content/zh/docs/reference/config/proxy_extensions/metadata_exchange/index.html +++ b/content/zh/docs/reference/config/proxy_extensions/metadata_exchange/index.html @@ -40,7 +40,6 @@

PluginConfig

google.protobuf.UInt32Value

Wrapper message for uint32.

-

The JSON representation for UInt32Value is JSON number.

diff --git a/content/zh/docs/reference/config/proxy_extensions/stackdriver/index.html b/content/zh/docs/reference/config/proxy_extensions/stackdriver/index.html index fc15e7ac6b01..90eaec5cf629 100644 --- a/content/zh/docs/reference/config/proxy_extensions/stackdriver/index.html +++ b/content/zh/docs/reference/config/proxy_extensions/stackdriver/index.html @@ -7,12 +7,12 @@ layout: protoc-gen-docs generator: protoc-gen-docs weight: 20 -number_of_entries: 3 +number_of_entries: 4 ---

CustomConfig

Custom instance configuration overrides. -Provides a way to customize metrics/logs.

+Provides a way to customize logs.

@@ -42,7 +42,7 @@

CustomConfig

PluginConfig

-

next id: 15

+

next id: 17

@@ -100,35 +100,6 @@

PluginConfig

productpage.default.svc.cluster.local. If not provided, request host header will be used instead

- - - - - - - - - - - - - - - - - - - + + + + + + @@ -232,6 +205,19 @@

PluginConfig

series will never be expired. This option is useful to avoid unbounded metric label explodes proxy memory.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
-No -
enable_mesh_edges_reportingbool -

Optional. Controls whether or not to export mesh edges to a mesh edges -service. This is disabled by default.

- -		 -No -
mesh_edges_reporting_durationDuration -

Optional. Allows configuration of the time between calls out to the mesh -edges service to report NEW edges. The minimum configurable duration is -10s. NOTE: This option ONLY configures the intermediate reporting of -novel edges. Once every 10m, all edges observed in that 10m window are -reported and the local cache is cleared. -The default duration is 1m. Any value greater than 10m will result in -reporting every 10m.

- 		No @@ -167,19 +138,6 @@

PluginConfig

Optional. Allows configuration of the number of traffic assertions to batch into a single request. Default is 100. Max is 1000.

-		 -No -
disable_http_size_metricsbool -

Optional. Allows disabling of reporting of the request and response size -metrics for HTTP traffic. Defaults to false (request and response size -metrics are enabled).

- 		No @@ -200,7 +158,21 @@

PluginConfig

access_logging AccessLogging -

Optional. Controls what type of logs to export..

+

Optional. Controls what type of logs to export.

+ +		 +No +
access_logging_filter_expressionstring +

CEL expression for filtering access logging. If the expression evaluates +to true, an access log entry will be generated. Otherwise, no access log +entry will be generated. +NOTE: Audit logs ignore configured filters.

 @@ -214,7 +186,8 @@

PluginConfig

(Optional) Collection of tag names and tag expressions to include in the logs. Conflicts are resolved by the tag name by overriding previously supplied values. Does not apply to audit logs. -See https://istio.io/latest/docs/tasks/observability/metrics/customize-metrics/#use-expressions-for-values +See +https://istio.io/latest/docs/tasks/observability/metrics/customize-metrics/#use-expressions-for-values for more details about the expression language.

 +No +
metrics_overridesmap<string, MetricsOverride> +

Optional. Allows altering metrics behavior. +Metric names for specifying overloads drop the istio.io/service prefix. +Examples: server/request_count, client/roundtrip_latencies

+ 		No @@ -244,6 +230,96 @@

PluginConfig

Optional. Controls whether to export server access log. This is deprecated in favor of AccessLogging enum.

+		 +No +
enable_mesh_edges_reportingbool +

Optional. Controls whether or not to export mesh edges to a mesh edges +service. This is disabled by default. +Deprecated – Mesh edge reporting is no longer supported and this setting +is no-op.

+ +		 +No +
mesh_edges_reporting_durationDuration +

Optional. Allows configuration of the time between calls out to the mesh +edges service to report NEW edges. The minimum configurable duration is +10s. NOTE: This option ONLY configures the intermediate reporting of +novel edges. Once every 10m, all edges observed in that 10m window are +reported and the local cache is cleared. +The default duration is 1m. Any value greater than 10m will result in +reporting every 10m. +Deprecated – Mesh edge reporting is no longer supported and this setting +is no-op.

+ +		 +No +
disable_http_size_metricsbool +

Optional. Allows disabling of reporting of the request and response size +metrics for HTTP traffic. Defaults to false (request and response size +metrics are enabled). +Deprecated – use metrics_overrides instead. +if metrics_overrides is used, this value will be ignored.

+ +		 +No +
+
+

MetricsOverride

+
+

Provides behavior modifications for Cloud Monitoring metrics.

+ + + + + + + + + + + + + + + + + + + + + diff --git a/content/zh/docs/reference/config/proxy_extensions/stats/index.html b/content/zh/docs/reference/config/proxy_extensions/stats/index.html index 37dbb855e658..5acd5cf8108e 100644 --- a/content/zh/docs/reference/config/proxy_extensions/stats/index.html +++ b/content/zh/docs/reference/config/proxy_extensions/stats/index.html @@ -7,7 +7,7 @@ layout: protoc-gen-docs generator: protoc-gen-docs weight: 20 -number_of_entries: 4 +number_of_entries: 5 ---

MetricConfig

@@ -70,6 +70,18 @@

MetricConfig

+ + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -245,6 +192,17 @@

PluginConfig

+ + + + + +
FieldTypeDescriptionRequired
dropbool +

Optional. If true, no data for the associated metric will be collected or +exported.

+ +		 +No +
tag_overridesmap<string, string> +

Optional. Maps tag names to value expressions that will be used at +reporting time. If the tag name does not match a well-known tag for the +istio Cloud Monitoring metrics, the configuration will have no effect.

+ 		No @@ -282,8 +358,7 @@

PluginConfig.AccessLogging

ERRORS_ONLY

All error logs. This is currently only available for outbound/client side -logs. A request is classified as error when status>=400 or -response_flag != "-"

+logs. A request is classified as error when status>=400 or response_flag != "-"

NOT IMPLEMENTED. (Optional) Conditional enabling the override.

+		 +No +
dropbool +

(Optional) If this is set to true, the metric(s) selected by this +configuration will not be generated or reported.

+ 		No @@ -138,71 +150,6 @@

PluginConfig

debugbool -

next id: 7 -The following settings should be rarely used. -Enable debug for this filter. -DEPRECATED.

- -		 -No -
max_peer_cache_sizeint32 -

maximum size of the peer metadata cache. -A long lived proxy that connects with many transient peers can build up a -large cache. To turn off the cache, set this field to a negative value. -DEPRECATED.

- -		 -No -
stat_prefixstring -

prefix to add to stats emitted by the plugin. -DEPRECATED.

- -		 -No -
field_separatorstring -

Stats api squashes dimensions in a single string. -The squashed string is parsed at prometheus scrape time to recover -dimensions. The following 2 fields set the field and value separators {key: -value} –> key{valueseparator}value{fieldseparator}

- -		 -No -
value_separatorstring -

default: “==”

- -		 -No -
disable_host_header_fallback bool

Metric definitions.

+		 +No +
reporterReporter +

Proxy deployment type.

+ 		No @@ -281,3 +239,33 @@

MetricType
+

Reporter

+
+

Specifies the proxy deployment type.

+ + + + + + + + + + + + + + + + + + +
NameDescription
UNSPECIFIED +

Default value is inferred from the listener direction, as either client or +server sidecar.

+ +
SERVER_GATEWAY +

Shared server gateway, e.g. “waypoint”.

+ +
+
diff --git a/content/zh/docs/reference/config/proxy_extensions/wasm-plugin/index.html b/content/zh/docs/reference/config/proxy_extensions/wasm-plugin/index.html index 8ef91625a53a..a83164be278d 100644 --- a/content/zh/docs/reference/config/proxy_extensions/wasm-plugin/index.html +++ b/content/zh/docs/reference/config/proxy_extensions/wasm-plugin/index.html @@ -8,7 +8,7 @@ generator: protoc-gen-docs schema: istio.extensions.v1alpha1.WasmPlugin aliases: [/zh/docs/reference/config/extensions/v1alpha1/wasm-plugin] -number_of_entries: 6 +number_of_entries: 7 ---

WasmPlugins provides a mechanism to extend the functionality provided by the Istio proxy through WebAssembly filters.

@@ -318,6 +318,19 @@

WasmPlugin

Configuration for a Wasm VM. more details can be found here.

+		 +No +
matchTrafficSelector[] +

Specifies the criteria to determine which traffic is passed to WasmPlugin. +If a traffic satisfies any of TrafficSelectors, +the traffic passes the WasmPlugin.

+ 		No @@ -400,6 +413,57 @@

EnvVar

Note that if value_from is HOST, it will be ignored. Defaults to “”.

+		 +No +
+ +

WasmPlugin.TrafficSelector

+
+

TrafficSelector provides a mechanism to select a specific traffic flow +for which this Wasm Plugin will be enabled. +When all the sub conditions in the TrafficSelector are satisfied, the +traffic will be selected.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescriptionRequired
modeWorkloadMode +

Criteria for selecting traffic by their direction. +Note that CLIENT and SERVER are analogous to INBOUND and OUTBOUND, +respectively. +For the gateway, the field should be CLIENT or CLIENT_AND_SERVER. +If not specified, the default value is CLIENT_AND_SERVER.

+ +		 +No +
portsPortSelector[] +

Criteria for selecting traffic by their destination port. +More specifically, for the outbound traffic, the destination port would be +the port of the target service. On the other hand, for the inbound traffic, +the destiation port is the port bound by the server process in the same Pod.

+

If one of the given ports is matched, this condition is evaluated to true. +If not specified, this condition is evaluated to true for any port.

+ 		No