From c21c4efa19d2e102116822c8060e91b40412b5b9 Mon Sep 17 00:00:00 2001 From: Istio Automation Date: Wed, 29 Dec 2021 18:48:18 -0800 Subject: [PATCH] Automator: update istio.io@ reference docs (#10696) --- .../reference/commands/istioctl/index.html | 4 +- .../networking/virtual-service/index.html | 13 ++- .../reference/config/telemetry/index.html | 95 ++++++++++++------- 3 files changed, 71 insertions(+), 41 deletions(-) diff --git a/content/en/docs/reference/commands/istioctl/index.html b/content/en/docs/reference/commands/istioctl/index.html index c0212f76d9..257c8fc789 100644 --- a/content/en/docs/reference/commands/istioctl/index.html +++ b/content/en/docs/reference/commands/istioctl/index.html @@ -405,7 +405,7 @@ All names except label and annotation keys support '*' glob matching pat --exclude <stringSlice> -Spec for which pod's proxy logs to exclude from the archive, after the include spec is processed. See above for format and examples. (default `["kube-system,kube-public,kube-node-lease,local-path-storage"]`) +Spec for which pod's proxy logs to exclude from the archive, after the include spec is processed. See above for format and examples. (default `["kube-node-lease,local-path-storage,kube-system,kube-public"]`) --filename <string> @@ -510,7 +510,7 @@ All names except label and annotation keys support '*' glob matching pat --exclude <stringSlice> -Spec for which pod's proxy logs to exclude from the archive, after the include spec is processed. See above for format and examples. (default `["kube-system,kube-public,kube-node-lease,local-path-storage"]`) +Spec for which pod's proxy logs to exclude from the archive, after the include spec is processed. See above for format and examples. (default `["kube-node-lease,local-path-storage,kube-system,kube-public"]`) --filename <string> diff --git a/content/en/docs/reference/config/networking/virtual-service/index.html b/content/en/docs/reference/config/networking/virtual-service/index.html index 528cb3bbc0..253b678e3e 100644 --- a/content/en/docs/reference/config/networking/virtual-service/index.html +++ b/content/en/docs/reference/config/networking/virtual-service/index.html @@ -1696,10 +1696,9 @@ Yes weight int32 -

The proportion of traffic to be forwarded to the service -version. (0-100). Sum of weights across destinations SHOULD BE == 100. -If there is only one destination in a rule, the weight value is assumed to -be 100.

+

Weight specifies the relative proportion of traffic to be forwarded to the destination. A destination will receive weight/(sum of all weights) requests. +If there is only one destination in a rule, it will receive all traffic. +Otherwise, if weight is 0, the destination will not receive any traffic.

@@ -1750,9 +1749,9 @@ Yes weight int32 -

The proportion of traffic to be forwarded to the service -version. If there is only one destination in a rule, all traffic will be -routed to it irrespective of the weight.

+

Weight specifies the relative proportion of traffic to be forwarded to the destination. A destination will receive weight/(sum of all weights) requests. +If there is only one destination in a rule, it will receive all traffic. +Otherwise, if weight is 0, the destination will not receive any traffic.

diff --git a/content/en/docs/reference/config/telemetry/index.html b/content/en/docs/reference/config/telemetry/index.html index 38ff16b3c0..e1cedf411c 100644 --- a/content/en/docs/reference/config/telemetry/index.html +++ b/content/en/docs/reference/config/telemetry/index.html @@ -21,10 +21,13 @@ to have a single workload selector-less Telemetry resource.

For resources with a workload selector, it is only valid to have one resource selecting any given workload.

-

The hierarchy of Telemetry configuration is as follows: -1. Workload-specific configuration -1. Namespace-specific configuration -1. Root namespace configuration

+

The hierarchy of Telemetry configuration is as follows:

+ +
    +
  1. Workload-specific configuration
    2. +
  2. Namespace-specific configuration
    3. +
  3. Root namespace configuration
    4. +

Examples:

@@ -828,10 +831,14 @@ No expression string -

CEL expression for selecting when requests/connections should be logged. -Examples: -- response.code >= 400 -- connection.mtls && request.url_path.contains('v1beta3')

+

CEL expression for selecting when requests/connections should be logged.

+ +

Examples:

+ + @@ -868,9 +875,12 @@ See also: https://istio.io/latest/docs/reference/config/metrics/#metrics

The Prometheus provider exports this metric as: istio_requests_total.

-

The Stackdriver provider exports this metric as: -- istio.io/service/server/request_count (SERVER mode) -- istio.io/service/client/request_count (CLIENT mode)

+

The Stackdriver provider exports this metric as:

+ + @@ -881,9 +891,12 @@ See also: https://istio.io/latest/docs/reference/config/metrics/#metrics

The Prometheus provider exports this metric as: istio_request_duration_milliseconds.

-

The Stackdriver provider exports this metric as: -- istio.io/service/server/response_latencies (SERVER mode) -- istio.io/service/client/roundtrip_latencies (CLIENT mode)

+

The Stackdriver provider exports this metric as:

+ + @@ -894,9 +907,12 @@ See also: https://istio.io/latest/docs/reference/config/metrics/#metrics

The Prometheus provider exports this metric as: istio_request_bytes.

-

The Stackdriver provider exports this metric as: -- istio.io/service/server/request_bytes (SERVER mode) -- istio.io/service/client/request_bytes (CLIENT mode)

+

The Stackdriver provider exports this metric as:

+ + @@ -907,9 +923,12 @@ See also: https://istio.io/latest/docs/reference/config/metrics/#metrics

The Prometheus provider exports this metric as: istio_response_bytes.

-

The Stackdriver provider exports this metric as: -- istio.io/service/server/response_bytes (SERVER mode) -- istio.io/service/client/response_bytes (CLIENT mode)

+

The Stackdriver provider exports this metric as:

+ + @@ -920,9 +939,12 @@ See also: https://istio.io/latest/docs/reference/config/metrics/#metrics

The Prometheus provider exports this metric as: istio_tcp_connections_opened_total.

-

The Stackdriver provider exports this metric as: -- istio.io/service/server/connection_open_count (SERVER mode) -- istio.io/service/client/connection_open_count (CLIENT mode)

+

The Stackdriver provider exports this metric as:

+ + @@ -933,9 +955,12 @@ See also: https://istio.io/latest/docs/reference/config/metrics/#metrics

The Prometheus provider exports this metric as: istio_tcp_connections_closed_total.

-

The Stackdriver provider exports this metric as: -- istio.io/service/server/connection_close_count (SERVER mode) -- istio.io/service/client/connection_close_count (CLIENT mode)

+

The Stackdriver provider exports this metric as:

+ + @@ -946,9 +971,12 @@ See also: https://istio.io/latest/docs/reference/config/metrics/#metrics

The Prometheus provider exports this metric as: istio_tcp_sent_bytes_total.

-

The Stackdriver provider exports this metric as: -- istio.io/service/server/sent_bytes_count (SERVER mode) -- istio.io/service/client/sent_bytes_count (CLIENT mode)

+

The Stackdriver provider exports this metric as:

+ + @@ -959,9 +987,12 @@ See also: https://istio.io/latest/docs/reference/config/metrics/#metrics

The Prometheus provider exports this metric as: istio_tcp_received_bytes_total.

-

The Stackdriver provider exports this metric as: -- istio.io/service/server/received_bytes_count (SERVER mode) -- istio.io/service/client/received_bytes_count (CLIENT mode)

+

The Stackdriver provider exports this metric as:

+ +