mirror of https://github.com/istio/istio.io.git
update_ref_docs fails on an arm machine (#13816)
* update_ref_docs fails on an arm machine * Remove retired ist0117 * Fix removed link
This commit is contained in:
Eric Van Norman
GitHub
parent
867381b258
commit
fbb5c8df9b
|
|
@ -23,7 +23,7 @@ This was a significant milestone, since it indicates that:
|
|||
|
||||
## `wasm-extensions` Ecosystem Repository
|
||||
|
||||
As an early adopter of the Envoy Wasm runtime, the Istio Extensions and Telemetry working group gained a lot of experience in developing extensions. We built several first-class extensions, including [metadata exchange](/docs/reference/config/proxy_extensions/metadata_exchange/), [Prometheus stats](https://archive.istio.io/v1.17/docs/reference/config/proxy_extensions/stats/), and [attribute generation](https://archive.istio.io/v1.17/docs/reference/config/proxy_extensions/attributegen/).
|
||||
As an early adopter of the Envoy Wasm runtime, the Istio Extensions and Telemetry working group gained a lot of experience in developing extensions. We built several first-class extensions, including [metadata exchange](https://archive.istio.io/v1.17/docs/reference/config/proxy_extensions/metadata_exchange/), [Prometheus stats](https://archive.istio.io/v1.17/docs/reference/config/proxy_extensions/stats/), and [attribute generation](https://archive.istio.io/v1.17/docs/reference/config/proxy_extensions/attributegen/).
|
||||
In order to share our learning more broadly, we created a [`wasm-extensions` repository](https://github.com/istio-ecosystem/wasm-extensions) in the `istio-ecosystem` organization. This repository serves two purposes:
|
||||
|
||||
* It provides canonical example extensions, covering several highly demanded features (such as [basic authentication](https://github.com/istio-ecosystem/wasm-extensions/tree/master/extensions/basic_auth)).
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
|
|
@ -1,12 +0,0 @@
|
|||
---
|
||||
title: DeploymentRequiresServiceAssociated
|
||||
layout: analysis-message
|
||||
owner: istio/wg-user-experience-maintainers
|
||||
test: no
|
||||
---
|
||||
|
||||
This message occurs when pods are not associated with any services.
|
||||
|
||||
A pod must belong to at least one Kubernetes service even if the pod does NOT expose any port.
|
||||
|
||||
See the [Istio Requirements](../../../../ops/deployment/requirements).
|
||||
|
|
@ -7,7 +7,7 @@ location: https://istio.io/docs/reference/config/istio.mesh.v1alpha1.html
|
|||
layout: protoc-gen-docs
|
||||
generator: protoc-gen-docs
|
||||
weight: 20
|
||||
number_of_entries: 64
|
||||
number_of_entries: 66
|
||||
---
|
||||
<p>Configuration affecting the service mesh as a whole.</p>
|
||||
|
||||
|
|
@ -67,26 +67,6 @@ No
|
|||
<p>Connection timeout used by Envoy. (MUST BE >=1ms)
|
||||
Default timeout is 10s.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="MeshConfig-protocol_detection_timeout">
|
||||
<td><code>protocolDetectionTimeout</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#duration">Duration</a></code></td>
|
||||
<td>
|
||||
<p>Automatic protocol detection uses a set of heuristics to
|
||||
determine whether the connection is using TLS or not (on the
|
||||
server side), as well as the application protocol being used
|
||||
(e.g., http vs tcp). These heuristics rely on the client sending
|
||||
the first bits of data. For server first protocols like MySQL,
|
||||
MongoDB, etc. Envoy will timeout on the protocol detection after
|
||||
the specified period, defaulting to non mTLS plain TCP
|
||||
traffic. Set this field to tweak the period that Envoy will wait
|
||||
for the client to send the first bits of data. (MUST BE >=1ms or
|
||||
0s to disable). Default detection timeout is 0s (no timeout).</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
|
|
@ -3152,6 +3132,8 @@ Note: currently all headers are enabled by default.</p>
|
|||
disabled: true
|
||||
envoyDebugHeaders:
|
||||
disabled: true
|
||||
metadataExchangeHeaders:
|
||||
mode: IN_MESH
|
||||
</code></pre>
|
||||
|
||||
</td>
|
||||
|
|
@ -3548,6 +3530,19 @@ If disabled, these headers will not be set. If they are already present, they wi
|
|||
See the <a href="https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/http/router/v3/router.proto#envoy-v3-api-field-extensions-filters-http-router-v3-router-suppress-envoy-headers">Envoy documentation</a> for more details.
|
||||
These headers are enabled by default if not configured.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="ProxyConfig-ProxyHeaders-metadata_exchange_headers">
|
||||
<td><code>metadataExchangeHeaders</code></td>
|
||||
<td><code><a href="#ProxyConfig-ProxyHeaders-MetadataExchangeHeaders">MetadataExchangeHeaders</a></code></td>
|
||||
<td>
|
||||
<p>Controls Istio metadata exchange headers <code>X-Envoy-Peer-Metadata</code> and <code>X-Envoy-Peer-Metadata-Id</code>.
|
||||
By default, the behavior is unspecified.
|
||||
If IN_MESH, these headers will not be appended to outbound requests from sidecars to services not in-mesh.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
|
|
@ -3663,6 +3658,30 @@ No
|
|||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="ProxyConfig-ProxyHeaders-MetadataExchangeHeaders">ProxyConfig.ProxyHeaders.MetadataExchangeHeaders</h2>
|
||||
<section>
|
||||
<table class="message-fields">
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Type</th>
|
||||
<th>Description</th>
|
||||
<th>Required</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="ProxyConfig-ProxyHeaders-MetadataExchangeHeaders-mode">
|
||||
<td><code>mode</code></td>
|
||||
<td><code><a href="#ProxyConfig-ProxyHeaders-MetadataExchangeMode">MetadataExchangeMode</a></code></td>
|
||||
<td>
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="Network">Network</h2>
|
||||
<section>
|
||||
<p>Network provides information about the endpoints in a routable L3
|
||||
|
|
@ -4227,6 +4246,34 @@ See the
|
|||
<a href="https://github.com/openzipkin/b3-propagation">B3 header propagation README</a>
|
||||
for details.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="ProxyConfig-ProxyHeaders-MetadataExchangeMode">ProxyConfig.ProxyHeaders.MetadataExchangeMode</h2>
|
||||
<section>
|
||||
<table class="enum-values">
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Name</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="ProxyConfig-ProxyHeaders-MetadataExchangeMode-UNDEFINED">
|
||||
<td><code>UNDEFINED</code></td>
|
||||
<td>
|
||||
<p>Existing Istio behavior for the metadata exchange headers is unchanged.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="ProxyConfig-ProxyHeaders-MetadataExchangeMode-IN_MESH">
|
||||
<td><code>IN_MESH</code></td>
|
||||
<td>
|
||||
<p>Only append the istio metadata exchange headers for services considered in-mesh.
|
||||
Traffic is considered in-mesh if it is secured with Istio mutual TLS. This means that <code>MESH_EXTERNAL</code> services, unmatched passthrough traffic, and requests to workloads without Istio enabled will be considered out of mesh.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
|
@ -4289,7 +4336,7 @@ outbound connections.</p>
|
|||
<td><code>REDIRECT</code></td>
|
||||
<td>
|
||||
<p>The <code>REDIRECT</code> mode uses iptables <code>REDIRECT</code> to <code>NAT</code> and redirect to Envoy. This mode loses
|
||||
source IP addresses during redirection.</p>
|
||||
source IP addresses during redirection. This is the default redirection mode.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ layout: protoc-gen-docs
|
|||
generator: protoc-gen-docs
|
||||
schema: istio.networking.v1alpha3.VirtualService
|
||||
aliases: [/docs/reference/config/networking/v1alpha3/virtual-service]
|
||||
number_of_entries: 28
|
||||
number_of_entries: 29
|
||||
---
|
||||
<p>Configuration affecting traffic routing. Here are a few terms useful to define
|
||||
in the context of traffic routing.</p>
|
||||
|
|
@ -729,6 +729,22 @@ mirrored cluster to respond before returning the response from the
|
|||
original destination. Statistics will be generated for the mirrored
|
||||
destination.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="HTTPRoute-mirrors">
|
||||
<td><code>mirrors</code></td>
|
||||
<td><code><a href="#HTTPMirrorPolicy">HTTPMirrorPolicy[]</a></code></td>
|
||||
<td>
|
||||
<p>Specifies the destinations to mirror HTTP traffic in addition
|
||||
to the original destination. Mirrored traffic is on a
|
||||
best effort basis where the sidecar/gateway will not wait for the
|
||||
mirrored destinations to respond before returning the response from the
|
||||
original destination. Statistics will be generated for the mirrored
|
||||
destination.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
|
|
@ -2495,7 +2511,8 @@ spec:
|
|||
between retries will be determined automatically (25ms+). When request
|
||||
<code>timeout</code> of the <a href="/docs/reference/config/networking/virtual-service/#HTTPRoute">HTTP route</a>
|
||||
or <code>per_try_timeout</code> is configured, the actual number of retries attempted also depends on
|
||||
the specified request <code>timeout</code> and <code>per_try_timeout</code> values.</p>
|
||||
the specified request <code>timeout</code> and <code>per_try_timeout</code> values. MUST BE >= 0. If <code>0</code>, retries will be disabled.
|
||||
The maximum possible number of requests made will be 1 + <code>attempts</code>.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
|
|
@ -2734,6 +2751,52 @@ No
|
|||
<p>Abort Http request attempts and return error codes back to downstream
|
||||
service, giving the impression that the upstream service is faulty.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="HTTPMirrorPolicy">HTTPMirrorPolicy</h2>
|
||||
<section>
|
||||
<p>HTTPMirrorPolicy can be used to specify the destinations to mirror HTTP traffic in addition
|
||||
to the original destination. Mirrored traffic is on a
|
||||
best effort basis where the sidecar/gateway will not wait for the
|
||||
mirrored destinations to respond before returning the response from the
|
||||
original destination. Statistics will be generated for the mirrored
|
||||
destination.</p>
|
||||
|
||||
<table class="message-fields">
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Type</th>
|
||||
<th>Description</th>
|
||||
<th>Required</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="HTTPMirrorPolicy-destination">
|
||||
<td><code>destination</code></td>
|
||||
<td><code><a href="#Destination">Destination</a></code></td>
|
||||
<td>
|
||||
<p>Destination specifies the target of the mirror operation.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
Yes
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="HTTPMirrorPolicy-percentage">
|
||||
<td><code>percentage</code></td>
|
||||
<td><code><a href="#Percent">Percent</a></code></td>
|
||||
<td>
|
||||
<p>Percentage of the traffic to be mirrored by the <code>destination</code> field.
|
||||
If this field is absent, all the traffic (100%) will be mirrored.
|
||||
Max value is 100.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
|
|
|
|||
|
|
@ -1,68 +0,0 @@
|
|||
---
|
||||
WARNING: THIS IS AN AUTO-GENERATED FILE, DO NOT EDIT. PLEASE MODIFY THE ORIGINAL SOURCE IN THE 'https://github.com/istio/proxy' REPO
|
||||
source_repo: https://github.com/istio/proxy
|
||||
title: Metadata Exchange Config
|
||||
description: Configuration for Metadata Exchange Filter.
|
||||
location: https://istio.io/docs/reference/config/proxy_extensions/metadata_exchange.html
|
||||
layout: protoc-gen-docs
|
||||
generator: protoc-gen-docs
|
||||
weight: 20
|
||||
number_of_entries: 2
|
||||
---
|
||||
<h2 id="PluginConfig">PluginConfig</h2>
|
||||
<section>
|
||||
<table class="message-fields">
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Type</th>
|
||||
<th>Description</th>
|
||||
<th>Required</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="PluginConfig-max_peer_cache_size">
|
||||
<td><code>max_peer_cache_size</code></td>
|
||||
<td><code><a href="#google-protobuf-UInt32Value">UInt32Value</a></code></td>
|
||||
<td>
|
||||
<p>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 zero.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="google-protobuf-UInt32Value">google.protobuf.UInt32Value</h2>
|
||||
<section>
|
||||
<p>Wrapper message for <code>uint32</code>.</p>
|
||||
<p>The JSON representation for <code>UInt32Value</code> is JSON number.</p>
|
||||
|
||||
<table class="message-fields">
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Type</th>
|
||||
<th>Description</th>
|
||||
<th>Required</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="google-protobuf-UInt32Value-value">
|
||||
<td><code>value</code></td>
|
||||
<td><code>uint32</code></td>
|
||||
<td>
|
||||
<p>The uint32 value.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
|
|
@ -8,7 +8,7 @@ layout: protoc-gen-docs
|
|||
generator: protoc-gen-docs
|
||||
schema: istio.extensions.v1alpha1.WasmPlugin
|
||||
aliases: [/docs/reference/config/extensions/v1alpha1/wasm-plugin]
|
||||
number_of_entries: 8
|
||||
number_of_entries: 9
|
||||
---
|
||||
<p>WasmPlugins provides a mechanism to extend the functionality provided by
|
||||
the Istio proxy through WebAssembly filters.</p>
|
||||
|
|
@ -342,6 +342,17 @@ No
|
|||
If a traffic satisfies any of TrafficSelectors,
|
||||
the traffic passes the WasmPlugin.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="WasmPlugin-type">
|
||||
<td><code>type</code></td>
|
||||
<td><code><a href="#PluginType">PluginType</a></code></td>
|
||||
<td>
|
||||
<p>Specifies the type of Wasm Extension to be used.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
|
|
@ -478,6 +489,50 @@ If not specified, this condition is evaluated to true for any port.</p>
|
|||
</td>
|
||||
<td>
|
||||
No
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="PluginType">PluginType</h2>
|
||||
<section>
|
||||
<p>PluginType indicates the type of Wasm Extension to be used.
|
||||
There are two types of Extensions: <code>HTTP</code> and <code>NETWORK</code>.
|
||||
HTTP Extension work at “Layer 7”(for example as an HTTP filters in Envoy).
|
||||
The detailed HTTP interface for can be found at [C++] (<a href="https://github.com/proxy-wasm/proxy-wasm-cpp-host/blob/b7e690703c7f26707438a2f1ebd7c197bc8f0296/include/proxy-wasm/context_interface.h#L199">https://github.com/proxy-wasm/proxy-wasm-cpp-host/blob/b7e690703c7f26707438a2f1ebd7c197bc8f0296/include/proxy-wasm/context_interface.h#L199</a>)
|
||||
and [Rust] (<a href="https://github.com/proxy-wasm/proxy-wasm-rust-sdk/blob/6b47aec926bc29971c727471d6f4c972ec407c7f/src/traits.rs#L309)">https://github.com/proxy-wasm/proxy-wasm-rust-sdk/blob/6b47aec926bc29971c727471d6f4c972ec407c7f/src/traits.rs#L309)</a>.
|
||||
NETWORK Extension work at “Layer 4”(for example, as a network filter in Envoy).
|
||||
The detailed NETWORK interface for can be found at [C++] (<a href="https://github.com/proxy-wasm/proxy-wasm-cpp-host/blob/b7e690703c7f26707438a2f1ebd7c197bc8f0296/include/proxy-wasm/context_interface.h#L257">https://github.com/proxy-wasm/proxy-wasm-cpp-host/blob/b7e690703c7f26707438a2f1ebd7c197bc8f0296/include/proxy-wasm/context_interface.h#L257</a>)
|
||||
and [Rust] (<a href="https://github.com/proxy-wasm/proxy-wasm-rust-sdk/blob/6b47aec926bc29971c727471d6f4c972ec407c7f/src/traits.rs#L257)">https://github.com/proxy-wasm/proxy-wasm-rust-sdk/blob/6b47aec926bc29971c727471d6f4c972ec407c7f/src/traits.rs#L257)</a>.
|
||||
The NETWORK Extension can be applied to HTTP traffic as well.</p>
|
||||
|
||||
<table class="enum-values">
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Name</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="PluginType-UNSPECIFIED_PLUGIN_TYPE">
|
||||
<td><code>UNSPECIFIED_PLUGIN_TYPE</code></td>
|
||||
<td>
|
||||
<p>Defaults to HTTP.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="PluginType-HTTP">
|
||||
<td><code>HTTP</code></td>
|
||||
<td>
|
||||
<p>Use HTTP Wasm Extension.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="PluginType-NETWORK">
|
||||
<td><code>NETWORK</code></td>
|
||||
<td>
|
||||
<p>Use Network Wasm Extension.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
|
|
|||
|
|
@ -266,8 +266,10 @@ spec:
|
|||
is now supported. A prefix ‘@’ is used to denote a match against internal metadata instead of the headers in the request.
|
||||
Currently this feature is only supported for the following metadata:</p>
|
||||
<ul>
|
||||
<li><code>request.auth.claims.{claim-name}[.{sub-claim}]*</code> which are extracted from validated JWT tokens. The claim name
|
||||
currently does not support the <code>.</code> character. Examples: <code>request.auth.claims.sub</code> and <code>request.auth.claims.name.givenName</code>.</li>
|
||||
<li><code>request.auth.claims.{claim-name}[.{nested-claim}]*</code> which are extracted from validated JWT tokens.
|
||||
Use the <code>.</code> or <code>[]</code> as a separator for nested claim names.
|
||||
Examples: <code>request.auth.claims.sub</code>, <code>request.auth.claims.name.givenName</code> and <code>request.auth.claims[foo.com/name]</code>.
|
||||
For more information, see <a href="/docs/tasks/security/authentication/jwt-route/">JWT claim based routing</a>.</li>
|
||||
</ul>
|
||||
<p>The use of matches against JWT claim metadata is only supported in Gateways. The following example shows:</p>
|
||||
<ul>
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
|
|
@ -1,12 +0,0 @@
|
|||
---
|
||||
title: DeploymentRequiresServiceAssociated
|
||||
layout: analysis-message
|
||||
owner: istio/wg-user-experience-maintainers
|
||||
test: no
|
||||
---
|
||||
|
||||
当 Pod 资源没有与任何 Service 资源相关联时会出现该问题。
|
||||
|
||||
一个 Pod 即使没有暴露任何端口也必须被至少一个 Kubernetes 的 Service 资源关联。
|
||||
|
||||
请查看 [Istio 要求](/zh/docs/ops/deployment/requirements/)来了解更多信息。
|
||||
|
|
@ -7,7 +7,7 @@ location: https://istio.io/docs/reference/config/istio.mesh.v1alpha1.html
|
|||
layout: protoc-gen-docs
|
||||
generator: protoc-gen-docs
|
||||
weight: 20
|
||||
number_of_entries: 64
|
||||
number_of_entries: 66
|
||||
---
|
||||
<p>Configuration affecting the service mesh as a whole.</p>
|
||||
|
||||
|
|
@ -67,26 +67,6 @@ No
|
|||
<p>Connection timeout used by Envoy. (MUST BE >=1ms)
|
||||
Default timeout is 10s.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="MeshConfig-protocol_detection_timeout">
|
||||
<td><code>protocolDetectionTimeout</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#duration">Duration</a></code></td>
|
||||
<td>
|
||||
<p>Automatic protocol detection uses a set of heuristics to
|
||||
determine whether the connection is using TLS or not (on the
|
||||
server side), as well as the application protocol being used
|
||||
(e.g., http vs tcp). These heuristics rely on the client sending
|
||||
the first bits of data. For server first protocols like MySQL,
|
||||
MongoDB, etc. Envoy will timeout on the protocol detection after
|
||||
the specified period, defaulting to non mTLS plain TCP
|
||||
traffic. Set this field to tweak the period that Envoy will wait
|
||||
for the client to send the first bits of data. (MUST BE >=1ms or
|
||||
0s to disable). Default detection timeout is 0s (no timeout).</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
|
|
@ -3152,6 +3132,8 @@ Note: currently all headers are enabled by default.</p>
|
|||
disabled: true
|
||||
envoyDebugHeaders:
|
||||
disabled: true
|
||||
metadataExchangeHeaders:
|
||||
mode: IN_MESH
|
||||
</code></pre>
|
||||
|
||||
</td>
|
||||
|
|
@ -3548,6 +3530,19 @@ If disabled, these headers will not be set. If they are already present, they wi
|
|||
See the <a href="https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/http/router/v3/router.proto#envoy-v3-api-field-extensions-filters-http-router-v3-router-suppress-envoy-headers">Envoy documentation</a> for more details.
|
||||
These headers are enabled by default if not configured.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="ProxyConfig-ProxyHeaders-metadata_exchange_headers">
|
||||
<td><code>metadataExchangeHeaders</code></td>
|
||||
<td><code><a href="#ProxyConfig-ProxyHeaders-MetadataExchangeHeaders">MetadataExchangeHeaders</a></code></td>
|
||||
<td>
|
||||
<p>Controls Istio metadata exchange headers <code>X-Envoy-Peer-Metadata</code> and <code>X-Envoy-Peer-Metadata-Id</code>.
|
||||
By default, the behavior is unspecified.
|
||||
If IN_MESH, these headers will not be appended to outbound requests from sidecars to services not in-mesh.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
|
|
@ -3663,6 +3658,30 @@ No
|
|||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="ProxyConfig-ProxyHeaders-MetadataExchangeHeaders">ProxyConfig.ProxyHeaders.MetadataExchangeHeaders</h2>
|
||||
<section>
|
||||
<table class="message-fields">
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Type</th>
|
||||
<th>Description</th>
|
||||
<th>Required</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="ProxyConfig-ProxyHeaders-MetadataExchangeHeaders-mode">
|
||||
<td><code>mode</code></td>
|
||||
<td><code><a href="#ProxyConfig-ProxyHeaders-MetadataExchangeMode">MetadataExchangeMode</a></code></td>
|
||||
<td>
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="Network">Network</h2>
|
||||
<section>
|
||||
<p>Network provides information about the endpoints in a routable L3
|
||||
|
|
@ -4227,6 +4246,34 @@ See the
|
|||
<a href="https://github.com/openzipkin/b3-propagation">B3 header propagation README</a>
|
||||
for details.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="ProxyConfig-ProxyHeaders-MetadataExchangeMode">ProxyConfig.ProxyHeaders.MetadataExchangeMode</h2>
|
||||
<section>
|
||||
<table class="enum-values">
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Name</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="ProxyConfig-ProxyHeaders-MetadataExchangeMode-UNDEFINED">
|
||||
<td><code>UNDEFINED</code></td>
|
||||
<td>
|
||||
<p>Existing Istio behavior for the metadata exchange headers is unchanged.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="ProxyConfig-ProxyHeaders-MetadataExchangeMode-IN_MESH">
|
||||
<td><code>IN_MESH</code></td>
|
||||
<td>
|
||||
<p>Only append the istio metadata exchange headers for services considered in-mesh.
|
||||
Traffic is considered in-mesh if it is secured with Istio mutual TLS. This means that <code>MESH_EXTERNAL</code> services, unmatched passthrough traffic, and requests to workloads without Istio enabled will be considered out of mesh.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
|
@ -4289,7 +4336,7 @@ outbound connections.</p>
|
|||
<td><code>REDIRECT</code></td>
|
||||
<td>
|
||||
<p>The <code>REDIRECT</code> mode uses iptables <code>REDIRECT</code> to <code>NAT</code> and redirect to Envoy. This mode loses
|
||||
source IP addresses during redirection.</p>
|
||||
source IP addresses during redirection. This is the default redirection mode.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ layout: protoc-gen-docs
|
|||
generator: protoc-gen-docs
|
||||
schema: istio.networking.v1alpha3.VirtualService
|
||||
aliases: [/zh/docs/reference/config/networking/v1alpha3/virtual-service]
|
||||
number_of_entries: 28
|
||||
number_of_entries: 29
|
||||
---
|
||||
<p>Configuration affecting traffic routing. Here are a few terms useful to define
|
||||
in the context of traffic routing.</p>
|
||||
|
|
@ -729,6 +729,22 @@ mirrored cluster to respond before returning the response from the
|
|||
original destination. Statistics will be generated for the mirrored
|
||||
destination.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="HTTPRoute-mirrors">
|
||||
<td><code>mirrors</code></td>
|
||||
<td><code><a href="#HTTPMirrorPolicy">HTTPMirrorPolicy[]</a></code></td>
|
||||
<td>
|
||||
<p>Specifies the destinations to mirror HTTP traffic in addition
|
||||
to the original destination. Mirrored traffic is on a
|
||||
best effort basis where the sidecar/gateway will not wait for the
|
||||
mirrored destinations to respond before returning the response from the
|
||||
original destination. Statistics will be generated for the mirrored
|
||||
destination.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
|
|
@ -2495,7 +2511,8 @@ spec:
|
|||
between retries will be determined automatically (25ms+). When request
|
||||
<code>timeout</code> of the <a href="/zh/docs/reference/config/networking/virtual-service/#HTTPRoute">HTTP route</a>
|
||||
or <code>per_try_timeout</code> is configured, the actual number of retries attempted also depends on
|
||||
the specified request <code>timeout</code> and <code>per_try_timeout</code> values.</p>
|
||||
the specified request <code>timeout</code> and <code>per_try_timeout</code> values. MUST BE >= 0. If <code>0</code>, retries will be disabled.
|
||||
The maximum possible number of requests made will be 1 + <code>attempts</code>.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
|
|
@ -2734,6 +2751,52 @@ No
|
|||
<p>Abort Http request attempts and return error codes back to downstream
|
||||
service, giving the impression that the upstream service is faulty.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="HTTPMirrorPolicy">HTTPMirrorPolicy</h2>
|
||||
<section>
|
||||
<p>HTTPMirrorPolicy can be used to specify the destinations to mirror HTTP traffic in addition
|
||||
to the original destination. Mirrored traffic is on a
|
||||
best effort basis where the sidecar/gateway will not wait for the
|
||||
mirrored destinations to respond before returning the response from the
|
||||
original destination. Statistics will be generated for the mirrored
|
||||
destination.</p>
|
||||
|
||||
<table class="message-fields">
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Type</th>
|
||||
<th>Description</th>
|
||||
<th>Required</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="HTTPMirrorPolicy-destination">
|
||||
<td><code>destination</code></td>
|
||||
<td><code><a href="#Destination">Destination</a></code></td>
|
||||
<td>
|
||||
<p>Destination specifies the target of the mirror operation.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
Yes
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="HTTPMirrorPolicy-percentage">
|
||||
<td><code>percentage</code></td>
|
||||
<td><code><a href="#Percent">Percent</a></code></td>
|
||||
<td>
|
||||
<p>Percentage of the traffic to be mirrored by the <code>destination</code> field.
|
||||
If this field is absent, all the traffic (100%) will be mirrored.
|
||||
Max value is 100.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
|
|
|
|||
|
|
@ -1,68 +0,0 @@
|
|||
---
|
||||
WARNING: THIS IS AN AUTO-GENERATED FILE, DO NOT EDIT. PLEASE MODIFY THE ORIGINAL SOURCE IN THE 'https://github.com/istio/proxy' REPO
|
||||
source_repo: https://github.com/istio/proxy
|
||||
title: Metadata Exchange Config
|
||||
description: Configuration for Metadata Exchange Filter.
|
||||
location: https://istio.io/docs/reference/config/proxy_extensions/metadata_exchange.html
|
||||
layout: protoc-gen-docs
|
||||
generator: protoc-gen-docs
|
||||
weight: 20
|
||||
number_of_entries: 2
|
||||
---
|
||||
<h2 id="PluginConfig">PluginConfig</h2>
|
||||
<section>
|
||||
<table class="message-fields">
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Type</th>
|
||||
<th>Description</th>
|
||||
<th>Required</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="PluginConfig-max_peer_cache_size">
|
||||
<td><code>max_peer_cache_size</code></td>
|
||||
<td><code><a href="#google-protobuf-UInt32Value">UInt32Value</a></code></td>
|
||||
<td>
|
||||
<p>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 zero.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="google-protobuf-UInt32Value">google.protobuf.UInt32Value</h2>
|
||||
<section>
|
||||
<p>Wrapper message for <code>uint32</code>.</p>
|
||||
<p>The JSON representation for <code>UInt32Value</code> is JSON number.</p>
|
||||
|
||||
<table class="message-fields">
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Type</th>
|
||||
<th>Description</th>
|
||||
<th>Required</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="google-protobuf-UInt32Value-value">
|
||||
<td><code>value</code></td>
|
||||
<td><code>uint32</code></td>
|
||||
<td>
|
||||
<p>The uint32 value.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
|
|
@ -8,7 +8,7 @@ layout: protoc-gen-docs
|
|||
generator: protoc-gen-docs
|
||||
schema: istio.extensions.v1alpha1.WasmPlugin
|
||||
aliases: [/zh/docs/reference/config/extensions/v1alpha1/wasm-plugin]
|
||||
number_of_entries: 8
|
||||
number_of_entries: 9
|
||||
---
|
||||
<p>WasmPlugins provides a mechanism to extend the functionality provided by
|
||||
the Istio proxy through WebAssembly filters.</p>
|
||||
|
|
@ -342,6 +342,17 @@ No
|
|||
If a traffic satisfies any of TrafficSelectors,
|
||||
the traffic passes the WasmPlugin.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="WasmPlugin-type">
|
||||
<td><code>type</code></td>
|
||||
<td><code><a href="#PluginType">PluginType</a></code></td>
|
||||
<td>
|
||||
<p>Specifies the type of Wasm Extension to be used.</p>
|
||||
|
||||
</td>
|
||||
<td>
|
||||
No
|
||||
|
|
@ -478,6 +489,50 @@ If not specified, this condition is evaluated to true for any port.</p>
|
|||
</td>
|
||||
<td>
|
||||
No
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="PluginType">PluginType</h2>
|
||||
<section>
|
||||
<p>PluginType indicates the type of Wasm Extension to be used.
|
||||
There are two types of Extensions: <code>HTTP</code> and <code>NETWORK</code>.
|
||||
HTTP Extension work at “Layer 7”(for example as an HTTP filters in Envoy).
|
||||
The detailed HTTP interface for can be found at [C++] (<a href="https://github.com/proxy-wasm/proxy-wasm-cpp-host/blob/b7e690703c7f26707438a2f1ebd7c197bc8f0296/include/proxy-wasm/context_interface.h#L199">https://github.com/proxy-wasm/proxy-wasm-cpp-host/blob/b7e690703c7f26707438a2f1ebd7c197bc8f0296/include/proxy-wasm/context_interface.h#L199</a>)
|
||||
and [Rust] (<a href="https://github.com/proxy-wasm/proxy-wasm-rust-sdk/blob/6b47aec926bc29971c727471d6f4c972ec407c7f/src/traits.rs#L309)">https://github.com/proxy-wasm/proxy-wasm-rust-sdk/blob/6b47aec926bc29971c727471d6f4c972ec407c7f/src/traits.rs#L309)</a>.
|
||||
NETWORK Extension work at “Layer 4”(for example, as a network filter in Envoy).
|
||||
The detailed NETWORK interface for can be found at [C++] (<a href="https://github.com/proxy-wasm/proxy-wasm-cpp-host/blob/b7e690703c7f26707438a2f1ebd7c197bc8f0296/include/proxy-wasm/context_interface.h#L257">https://github.com/proxy-wasm/proxy-wasm-cpp-host/blob/b7e690703c7f26707438a2f1ebd7c197bc8f0296/include/proxy-wasm/context_interface.h#L257</a>)
|
||||
and [Rust] (<a href="https://github.com/proxy-wasm/proxy-wasm-rust-sdk/blob/6b47aec926bc29971c727471d6f4c972ec407c7f/src/traits.rs#L257)">https://github.com/proxy-wasm/proxy-wasm-rust-sdk/blob/6b47aec926bc29971c727471d6f4c972ec407c7f/src/traits.rs#L257)</a>.
|
||||
The NETWORK Extension can be applied to HTTP traffic as well.</p>
|
||||
|
||||
<table class="enum-values">
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Name</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="PluginType-UNSPECIFIED_PLUGIN_TYPE">
|
||||
<td><code>UNSPECIFIED_PLUGIN_TYPE</code></td>
|
||||
<td>
|
||||
<p>Defaults to HTTP.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="PluginType-HTTP">
|
||||
<td><code>HTTP</code></td>
|
||||
<td>
|
||||
<p>Use HTTP Wasm Extension.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="PluginType-NETWORK">
|
||||
<td><code>NETWORK</code></td>
|
||||
<td>
|
||||
<p>Use Network Wasm Extension.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
|
|
|||
|
|
@ -266,8 +266,10 @@ spec:
|
|||
is now supported. A prefix ‘@’ is used to denote a match against internal metadata instead of the headers in the request.
|
||||
Currently this feature is only supported for the following metadata:</p>
|
||||
<ul>
|
||||
<li><code>request.auth.claims.{claim-name}[.{sub-claim}]*</code> which are extracted from validated JWT tokens. The claim name
|
||||
currently does not support the <code>.</code> character. Examples: <code>request.auth.claims.sub</code> and <code>request.auth.claims.name.givenName</code>.</li>
|
||||
<li><code>request.auth.claims.{claim-name}[.{nested-claim}]*</code> which are extracted from validated JWT tokens.
|
||||
Use the <code>.</code> or <code>[]</code> as a separator for nested claim names.
|
||||
Examples: <code>request.auth.claims.sub</code>, <code>request.auth.claims.name.givenName</code> and <code>request.auth.claims[foo.com/name]</code>.
|
||||
For more information, see <a href="/latest/docs/tasks/security/authentication/jwt-route/">JWT claim based routing</a>.</li>
|
||||
</ul>
|
||||
<p>The use of matches against JWT claim metadata is only supported in Gateways. The following example shows:</p>
|
||||
<ul>
|
||||
|
|
|
|||
|
|
@ -171,11 +171,7 @@ messages:
|
|||
- name: services
|
||||
type: "[]string"
|
||||
|
||||
- name: "DeploymentRequiresServiceAssociated"
|
||||
code: IST0117
|
||||
level: Warning
|
||||
description: "The resulting pods of a service mesh deployment must be associated with at least one service."
|
||||
template: "No service associated with this deployment. Service mesh deployments must be associated with a service."
|
||||
# IST0117 RETIRED
|
||||
|
||||
- name: "PortNameIsNotUnderNamingConvention"
|
||||
code: IST0118
|
||||
|
|
|
|||
|
|
@ -60,7 +60,6 @@ COMP_OUTPUT_DIR="${ROOTDIR}/content/en/docs/reference/commands"
|
|||
COMP_OUTPUT_DIR_ZH="${ROOTDIR}/content/zh/docs/reference/commands"
|
||||
|
||||
export GOOS=linux
|
||||
export GOARCH=amd64
|
||||
|
||||
echo "WORK_DIR =" "${WORK_DIR}"
|
||||
|
||||
|
|
@ -158,6 +157,7 @@ handle_components() {
|
|||
|
||||
go build -o "${COMP_NAME}"
|
||||
mkdir -p "${COMP_OUTPUT_DIR}/${COMP_NAME}"
|
||||
mkdir -p "${COMP_OUTPUT_DIR_ZH}/${COMP_NAME}"
|
||||
"./${COMP_NAME}" collateral -o "${COMP_OUTPUT_DIR}/${COMP_NAME}" --html_fragment_with_front_matter
|
||||
cp "${COMP_OUTPUT_DIR}/${COMP_NAME}/${COMP_NAME}.html" "${COMP_OUTPUT_DIR}/${COMP_NAME}/index.html"
|
||||
mv "${COMP_OUTPUT_DIR}/${COMP_NAME}/${COMP_NAME}.html" "${COMP_OUTPUT_DIR_ZH}/${COMP_NAME}/index.html"
|
||||
|
|
|
|||
|
|
@ -59,7 +59,6 @@ WORK_DIR="$(mktemp -d)"
|
|||
COMP_OUTPUT_DIR="${ROOTDIR}/content/zh/docs/reference/commands"
|
||||
|
||||
export GOOS=linux
|
||||
export GOARCH=amd64
|
||||
|
||||
echo "WORK_DIR =" "${WORK_DIR}"
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue