mirror of https://github.com/istio/istio.io.git
Update reference docs
This commit is contained in:
mtail
parent
9f3e980147
commit
5bfc6bafea
|
|
@ -35,7 +35,7 @@ Istio telemetry pipeline, just like services in the mesh.
|
|||
Helm or `istioctl gen-deploy`, users can install only the features they want. For example, users can install Pilot only and enjoy traffic
|
||||
management functionality without dealing with Mixer or Citadel.
|
||||
Learn more about [customization through Helm](/docs/setup/kubernetes/helm-install/#customization-with-helm)
|
||||
and about [`istioctl gen-deploy`](/docs/reference/commands/istioctl/#istioctl%20gen-deploy).
|
||||
and about [`istioctl gen-deploy`](/docs/reference/commands/istioctl/#istioctl-gen-deploy).
|
||||
|
||||
## Mixer adapters
|
||||
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ traffic has proven to be woefully insufficient for our needs.
|
|||
To address these, and other concerns, a new traffic management API, a.k.a. `v1alpha3`, is being introduced, which will
|
||||
completely replace the previous API going forward. Although the `v1alpha3` model is fundamentally the same, it is not
|
||||
backward compatible and will require manual conversion from the old API. A
|
||||
[conversion tool](/docs/reference/commands/istioctl/#istioctl%20experimental%20convert-networking-config)
|
||||
[conversion tool](/docs/reference/commands/istioctl/#istioctl-experimental-convert-networking-config)
|
||||
is included in the next few releases of Istio to help with the transition.
|
||||
|
||||
To justify this disruption, the `v1alpha3` API has gone through a long and painstaking community
|
||||
|
|
|
|||
|
|
@ -88,7 +88,7 @@ To start the application, follow the instructions below corresponding to your Is
|
|||
```
|
||||
|
||||
The `istioctl kube-inject` command is used to manually modify the `bookinfo.yaml`
|
||||
file before creating the deployments as documented [here](/docs/reference/commands/istioctl/#istioctl kube-inject).
|
||||
file before creating the deployments as documented [here](/docs/reference/commands/istioctl/#istioctl-kube-inject).
|
||||
|
||||
* If you are using a cluster with
|
||||
[automatic sidecar injection](/docs/setup/kubernetes/sidecar-injection/#automatic-sidecar-injection)
|
||||
|
|
|
|||
|
|
@ -167,7 +167,7 @@ number_of_entries: 4
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="istio_ca probe">istio_ca probe</h2>
|
||||
<h2 id="istio_ca-probe">istio_ca probe</h2>
|
||||
<p>Check the liveness or readiness of a locally-running server</p>
|
||||
<pre class="language-bash"><code>istio_ca probe [flags]
|
||||
</code></pre>
|
||||
|
|
@ -223,7 +223,7 @@ number_of_entries: 4
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="istio_ca version">istio_ca version</h2>
|
||||
<h2 id="istio_ca-version">istio_ca version</h2>
|
||||
<p>Prints out build version information</p>
|
||||
<pre class="language-bash"><code>istio_ca version [flags]
|
||||
</code></pre>
|
||||
|
|
|
|||
|
|
@ -22,6 +22,11 @@ system.</p>
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--context <string></code></td>
|
||||
<td></td>
|
||||
<td>The name of the kubeconfig context to use (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--istioNamespace <string></code></td>
|
||||
<td><code>-i</code></td>
|
||||
<td>Istio system namespace (default `istio-system`)</td>
|
||||
|
|
@ -29,7 +34,7 @@ system.</p>
|
|||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td><code>-c</code></td>
|
||||
<td>Kubernetes configuration file (default `$KUBECONFIG else $HOME/.kube/config`)</td>
|
||||
<td>Kubernetes configuration file (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--log_as_json</code></td>
|
||||
|
|
@ -88,7 +93,7 @@ system.</p>
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="istioctl context-create">istioctl context-create</h2>
|
||||
<h2 id="istioctl-context-create">istioctl context-create</h2>
|
||||
<p>Create a kubeconfig file suitable for use with istioctl in a non kubernetes environment</p>
|
||||
<pre class="language-bash"><code>istioctl context-create --api-server http://<ip>:<port> [flags]
|
||||
</code></pre>
|
||||
|
|
@ -107,7 +112,7 @@ system.</p>
|
|||
<tr>
|
||||
<td><code>--context <string></code></td>
|
||||
<td></td>
|
||||
<td>Kubernetes configuration file context name (default `istio`)</td>
|
||||
<td>The name of the kubeconfig context to use (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--istioNamespace <string></code></td>
|
||||
|
|
@ -117,7 +122,7 @@ system.</p>
|
|||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td><code>-c</code></td>
|
||||
<td>Kubernetes configuration file (default `$KUBECONFIG else $HOME/.kube/config`)</td>
|
||||
<td>Kubernetes configuration file (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--log_as_json</code></td>
|
||||
|
|
@ -176,12 +181,12 @@ system.</p>
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="istioctl context-create Examples">Examples</h3>
|
||||
<h3 id="istioctl-context-create Examples">Examples</h3>
|
||||
<pre class="language-bash"><code># Create a config file for the api server.
|
||||
istioctl context-create --api-server http://127.0.0.1:8080
|
||||
|
||||
</code></pre>
|
||||
<h2 id="istioctl create">istioctl create</h2>
|
||||
<h2 id="istioctl-create">istioctl create</h2>
|
||||
<p>Create policies and rules</p>
|
||||
<pre class="language-bash"><code>istioctl create [flags]
|
||||
</code></pre>
|
||||
|
|
@ -193,6 +198,11 @@ istioctl context-create --api-server http://127.0.0.1:8080
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--context <string></code></td>
|
||||
<td></td>
|
||||
<td>The name of the kubeconfig context to use (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--file <string></code></td>
|
||||
<td><code>-f</code></td>
|
||||
<td>Input file with the content of the configuration objects (if not set, command reads from the standard input) (default ``)</td>
|
||||
|
|
@ -205,7 +215,7 @@ istioctl context-create --api-server http://127.0.0.1:8080
|
|||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td><code>-c</code></td>
|
||||
<td>Kubernetes configuration file (default `$KUBECONFIG else $HOME/.kube/config`)</td>
|
||||
<td>Kubernetes configuration file (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--log_as_json</code></td>
|
||||
|
|
@ -264,10 +274,10 @@ istioctl context-create --api-server http://127.0.0.1:8080
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="istioctl create Examples">Examples</h3>
|
||||
<h3 id="istioctl-create Examples">Examples</h3>
|
||||
<pre class="language-bash"><code>istioctl create -f example-routing.yaml
|
||||
</code></pre>
|
||||
<h2 id="istioctl delete">istioctl delete</h2>
|
||||
<h2 id="istioctl-delete">istioctl delete</h2>
|
||||
<p>Delete policies or rules</p>
|
||||
<pre class="language-bash"><code>istioctl delete <type> <name> [<name2> ... <nameN>] [flags]
|
||||
</code></pre>
|
||||
|
|
@ -279,6 +289,11 @@ istioctl context-create --api-server http://127.0.0.1:8080
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--context <string></code></td>
|
||||
<td></td>
|
||||
<td>The name of the kubeconfig context to use (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--file <string></code></td>
|
||||
<td><code>-f</code></td>
|
||||
<td>Input file with the content of the configuration objects (if not set, command reads from the standard input) (default ``)</td>
|
||||
|
|
@ -291,7 +306,7 @@ istioctl context-create --api-server http://127.0.0.1:8080
|
|||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td><code>-c</code></td>
|
||||
<td>Kubernetes configuration file (default `$KUBECONFIG else $HOME/.kube/config`)</td>
|
||||
<td>Kubernetes configuration file (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--log_as_json</code></td>
|
||||
|
|
@ -350,7 +365,7 @@ istioctl context-create --api-server http://127.0.0.1:8080
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="istioctl delete Examples">Examples</h3>
|
||||
<h3 id="istioctl-delete Examples">Examples</h3>
|
||||
<pre class="language-bash"><code># Delete a rule using the definition in example-routing.yaml.
|
||||
istioctl delete -f example-routing.yaml
|
||||
|
||||
|
|
@ -358,7 +373,7 @@ istioctl delete -f example-routing.yaml
|
|||
istioctl delete virtualservice bookinfo
|
||||
|
||||
</code></pre>
|
||||
<h2 id="istioctl deregister">istioctl deregister</h2>
|
||||
<h2 id="istioctl-deregister">istioctl deregister</h2>
|
||||
<p>De-registers a service instance</p>
|
||||
<pre class="language-bash"><code>istioctl deregister <svcname> <ip> [flags]
|
||||
</code></pre>
|
||||
|
|
@ -370,6 +385,11 @@ istioctl delete virtualservice bookinfo
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--context <string></code></td>
|
||||
<td></td>
|
||||
<td>The name of the kubeconfig context to use (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--istioNamespace <string></code></td>
|
||||
<td><code>-i</code></td>
|
||||
<td>Istio system namespace (default `istio-system`)</td>
|
||||
|
|
@ -377,7 +397,7 @@ istioctl delete virtualservice bookinfo
|
|||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td><code>-c</code></td>
|
||||
<td>Kubernetes configuration file (default `$KUBECONFIG else $HOME/.kube/config`)</td>
|
||||
<td>Kubernetes configuration file (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--log_as_json</code></td>
|
||||
|
|
@ -436,7 +456,7 @@ istioctl delete virtualservice bookinfo
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="istioctl experimental">istioctl experimental</h2>
|
||||
<h2 id="istioctl-experimental">istioctl experimental</h2>
|
||||
<p>Experimental commands that may be modified or deprecated</p>
|
||||
<table class="command-flags">
|
||||
<thead>
|
||||
|
|
@ -446,6 +466,11 @@ istioctl delete virtualservice bookinfo
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--context <string></code></td>
|
||||
<td></td>
|
||||
<td>The name of the kubeconfig context to use (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--istioNamespace <string></code></td>
|
||||
<td><code>-i</code></td>
|
||||
<td>Istio system namespace (default `istio-system`)</td>
|
||||
|
|
@ -453,7 +478,7 @@ istioctl delete virtualservice bookinfo
|
|||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td><code>-c</code></td>
|
||||
<td>Kubernetes configuration file (default `$KUBECONFIG else $HOME/.kube/config`)</td>
|
||||
<td>Kubernetes configuration file (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--log_as_json</code></td>
|
||||
|
|
@ -512,7 +537,7 @@ istioctl delete virtualservice bookinfo
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="istioctl experimental convert-networking-config">istioctl experimental convert-networking-config</h2>
|
||||
<h2 id="istioctl-experimental-convert-networking-config">istioctl experimental convert-networking-config</h2>
|
||||
<p>Converts sets of v1alpha1 configs to v1alpha3 equivalents on a best effort basis. The output should be considered a starting point for your v1alpha3 configs and probably require some minor modification. Warnings will (hopefully) be generated where configs cannot be converted perfectly, or in certain edge cases. The input must be the set of configs that would be in place in an environment at a given time. This allows the command to attempt to create and merge output configs intelligently.Output configs are given the namespace and domain of the first input config so it is recommended that input configs be part of the same namespace and domain.</p>
|
||||
<pre class="language-bash"><code>istioctl experimental convert-networking-config [flags]
|
||||
</code></pre>
|
||||
|
|
@ -524,6 +549,11 @@ istioctl delete virtualservice bookinfo
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--context <string></code></td>
|
||||
<td></td>
|
||||
<td>The name of the kubeconfig context to use (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--filenames <stringSlice></code></td>
|
||||
<td><code>-f</code></td>
|
||||
<td>Input filenames (default `[]`)</td>
|
||||
|
|
@ -536,7 +566,7 @@ istioctl delete virtualservice bookinfo
|
|||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td><code>-c</code></td>
|
||||
<td>Kubernetes configuration file (default `$KUBECONFIG else $HOME/.kube/config`)</td>
|
||||
<td>Kubernetes configuration file (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--log_as_json</code></td>
|
||||
|
|
@ -600,10 +630,10 @@ istioctl delete virtualservice bookinfo
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="istioctl experimental convert-networking-config Examples">Examples</h3>
|
||||
<h3 id="istioctl-experimental-convert-networking-config Examples">Examples</h3>
|
||||
<pre class="language-bash"><code>istioctl experimental convert-networking-config -f v1alpha1/default-route.yaml -f v1alpha1/header-delay.yaml
|
||||
</code></pre>
|
||||
<h2 id="istioctl experimental metrics">istioctl experimental metrics</h2>
|
||||
<h2 id="istioctl-experimental-metrics">istioctl experimental metrics</h2>
|
||||
<p>
|
||||
Prints the metrics for the specified service(s) when running in Kubernetes.</p>
|
||||
<p>This command finds a Prometheus pod running in the specified istio system
|
||||
|
|
@ -626,6 +656,11 @@ calculated over a time interval of 1 minute.
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--context <string></code></td>
|
||||
<td></td>
|
||||
<td>The name of the kubeconfig context to use (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--istioNamespace <string></code></td>
|
||||
<td><code>-i</code></td>
|
||||
<td>Istio system namespace (default `istio-system`)</td>
|
||||
|
|
@ -633,7 +668,7 @@ calculated over a time interval of 1 minute.
|
|||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td><code>-c</code></td>
|
||||
<td>Kubernetes configuration file (default `$KUBECONFIG else $HOME/.kube/config`)</td>
|
||||
<td>Kubernetes configuration file (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--log_as_json</code></td>
|
||||
|
|
@ -692,7 +727,7 @@ calculated over a time interval of 1 minute.
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="istioctl experimental metrics Examples">Examples</h3>
|
||||
<h3 id="istioctl-experimental-metrics Examples">Examples</h3>
|
||||
<pre class="language-bash"><code>
|
||||
# Retrieve service metrics for productpage service
|
||||
istioctl experimental metrics productpage
|
||||
|
|
@ -701,7 +736,7 @@ istioctl experimental metrics productpage
|
|||
istioctl experimental metrics productpage.foo reviews.bar ratings.baz
|
||||
|
||||
</code></pre>
|
||||
<h2 id="istioctl experimental rbac">istioctl experimental rbac</h2>
|
||||
<h2 id="istioctl-experimental-rbac">istioctl experimental rbac</h2>
|
||||
<p>
|
||||
A group of commands used to interact with Istio RBAC policies. For example, Query whether a specific
|
||||
request is allowed or denied under the current Istio RBAC policies.</p>
|
||||
|
|
@ -713,6 +748,11 @@ request is allowed or denied under the current Istio RBAC policies.</p>
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--context <string></code></td>
|
||||
<td></td>
|
||||
<td>The name of the kubeconfig context to use (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--istioNamespace <string></code></td>
|
||||
<td><code>-i</code></td>
|
||||
<td>Istio system namespace (default `istio-system`)</td>
|
||||
|
|
@ -720,7 +760,7 @@ request is allowed or denied under the current Istio RBAC policies.</p>
|
|||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td><code>-c</code></td>
|
||||
<td>Kubernetes configuration file (default `$KUBECONFIG else $HOME/.kube/config`)</td>
|
||||
<td>Kubernetes configuration file (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--log_as_json</code></td>
|
||||
|
|
@ -779,11 +819,11 @@ request is allowed or denied under the current Istio RBAC policies.</p>
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="istioctl experimental rbac Examples">Examples</h3>
|
||||
<h3 id="istioctl-experimental-rbac Examples">Examples</h3>
|
||||
<pre class="language-bash"><code># Query if user test is allowed to GET /v1/health of service rating.
|
||||
istioctl experimental rbac can -u test GET rating /v1/health
|
||||
</code></pre>
|
||||
<h2 id="istioctl experimental rbac can">istioctl experimental rbac can</h2>
|
||||
<h2 id="istioctl-experimental-rbac-can">istioctl experimental rbac can</h2>
|
||||
<p>
|
||||
This command lets you query whether a specific request will be allowed or denied under current Istio
|
||||
RBAC policies. It constructs a fake request with the custom subject and action specified in the command
|
||||
|
|
@ -806,6 +846,11 @@ is being taken on. PATH is the HTTP path within the service.</p>
|
|||
<td>[Action] Additional data about the action. Specified as name1=value1,name2=value2,... (default `[]`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--context <string></code></td>
|
||||
<td></td>
|
||||
<td>The name of the kubeconfig context to use (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--groups <string></code></td>
|
||||
<td><code>-g</code></td>
|
||||
<td>[Subject] Group name/ID that the subject represents. (default ``)</td>
|
||||
|
|
@ -818,7 +863,7 @@ is being taken on. PATH is the HTTP path within the service.</p>
|
|||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td><code>-c</code></td>
|
||||
<td>Kubernetes configuration file (default `$KUBECONFIG else $HOME/.kube/config`)</td>
|
||||
<td>Kubernetes configuration file (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--log_as_json</code></td>
|
||||
|
|
@ -887,14 +932,14 @@ is being taken on. PATH is the HTTP path within the service.</p>
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="istioctl experimental rbac can Examples">Examples</h3>
|
||||
<h3 id="istioctl-experimental-rbac-can Examples">Examples</h3>
|
||||
<pre class="language-bash"><code># Query if user test is allowed to GET /v1/health of service rating.
|
||||
istioctl experimental rbac can -u test GET rating /v1/health
|
||||
|
||||
# Query if service product-page is allowed to POST to /data of service rating with label version=dev.
|
||||
istioctl experimental rbac can -s service=product-page POST rating /data -a version=dev
|
||||
</code></pre>
|
||||
<h2 id="istioctl gen-deploy">istioctl gen-deploy</h2>
|
||||
<h2 id="istioctl-gen-deploy">istioctl gen-deploy</h2>
|
||||
<p>istioctl gen-deploy produces deployment files to run the Istio.</p>
|
||||
<pre class="language-bash"><code>istioctl gen-deploy [flags]
|
||||
</code></pre>
|
||||
|
|
@ -906,6 +951,11 @@ istioctl experimental rbac can -s service=product-page POST rating /data -a vers
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--context <string></code></td>
|
||||
<td></td>
|
||||
<td>The name of the kubeconfig context to use (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--debug</code></td>
|
||||
<td></td>
|
||||
<td>If true, uses debug images instead of release images </td>
|
||||
|
|
@ -938,7 +988,7 @@ istioctl experimental rbac can -s service=product-page POST rating /data -a vers
|
|||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td><code>-c</code></td>
|
||||
<td>Kubernetes configuration file (default `$KUBECONFIG else $HOME/.kube/config`)</td>
|
||||
<td>Kubernetes configuration file (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--log_as_json</code></td>
|
||||
|
|
@ -1002,10 +1052,10 @@ istioctl experimental rbac can -s service=product-page POST rating /data -a vers
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="istioctl gen-deploy Examples">Examples</h3>
|
||||
<h3 id="istioctl-gen-deploy Examples">Examples</h3>
|
||||
<pre class="language-bash"><code>istioctl gen-deploy --values myvalues.yaml
|
||||
</code></pre>
|
||||
<h2 id="istioctl get">istioctl get</h2>
|
||||
<h2 id="istioctl-get">istioctl get</h2>
|
||||
<p>Retrieve policies and rules</p>
|
||||
<pre class="language-bash"><code>istioctl get <type> [<name>] [flags]
|
||||
</code></pre>
|
||||
|
|
@ -1017,6 +1067,16 @@ istioctl experimental rbac can -s service=product-page POST rating /data -a vers
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--all-namespaces</code></td>
|
||||
<td></td>
|
||||
<td>If present, list the requested object(s) across all namespaces. Namespace in current context is ignored even if specified with --namespace. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--context <string></code></td>
|
||||
<td></td>
|
||||
<td>The name of the kubeconfig context to use (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--istioNamespace <string></code></td>
|
||||
<td><code>-i</code></td>
|
||||
<td>Istio system namespace (default `istio-system`)</td>
|
||||
|
|
@ -1024,7 +1084,7 @@ istioctl experimental rbac can -s service=product-page POST rating /data -a vers
|
|||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td><code>-c</code></td>
|
||||
<td>Kubernetes configuration file (default `$KUBECONFIG else $HOME/.kube/config`)</td>
|
||||
<td>Kubernetes configuration file (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--log_as_json</code></td>
|
||||
|
|
@ -1088,7 +1148,7 @@ istioctl experimental rbac can -s service=product-page POST rating /data -a vers
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="istioctl get Examples">Examples</h3>
|
||||
<h3 id="istioctl-get Examples">Examples</h3>
|
||||
<pre class="language-bash"><code># List all virtual services
|
||||
istioctl get virtualservices
|
||||
|
||||
|
|
@ -1099,7 +1159,7 @@ istioctl get destinationrules
|
|||
istioctl get virtualservice bookinfo
|
||||
|
||||
</code></pre>
|
||||
<h2 id="istioctl kube-inject">istioctl kube-inject</h2>
|
||||
<h2 id="istioctl-kube-inject">istioctl kube-inject</h2>
|
||||
<p></p>
|
||||
<p>kube-inject manually injects envoy sidecar into kubernetes
|
||||
workloads. Unsupported resources are left unmodified so it is safe to
|
||||
|
|
@ -1129,6 +1189,11 @@ file/configmap created with a new Istio release.
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--context <string></code></td>
|
||||
<td></td>
|
||||
<td>The name of the kubeconfig context to use (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--filename <string></code></td>
|
||||
<td><code>-f</code></td>
|
||||
<td>Input Kubernetes resource filename (default ``)</td>
|
||||
|
|
@ -1151,7 +1216,7 @@ file/configmap created with a new Istio release.
|
|||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td><code>-c</code></td>
|
||||
<td>Kubernetes configuration file (default `$KUBECONFIG else $HOME/.kube/config`)</td>
|
||||
<td>Kubernetes configuration file (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--log_as_json</code></td>
|
||||
|
|
@ -1225,7 +1290,7 @@ file/configmap created with a new Istio release.
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="istioctl kube-inject Examples">Examples</h3>
|
||||
<h3 id="istioctl-kube-inject Examples">Examples</h3>
|
||||
<pre class="language-bash"><code>
|
||||
# Update resources on the fly before applying.
|
||||
kubectl apply -f <(istioctl kube-inject -f <resource.yaml>)
|
||||
|
|
@ -1242,7 +1307,7 @@ kubectl get deployment -o yaml | istioctl kube-inject -f - | kubectl apply -f -
|
|||
istioctl kube-inject -f deployment.yaml -o deployment-injected.yaml --injectConfigMapName istio-inject
|
||||
|
||||
</code></pre>
|
||||
<h2 id="istioctl proxy-config">istioctl proxy-config</h2>
|
||||
<h2 id="istioctl-proxy-config">istioctl proxy-config</h2>
|
||||
<p>
|
||||
Retrieves proxy configuration for the specified pod from the endpoint proxy or Pilot when running in Kubernetes.
|
||||
It is also able to retrieve the state of the entire mesh by using mesh instead of <pod-name>. This is only available when querying Pilot.</p>
|
||||
|
|
@ -1262,6 +1327,11 @@ It is also able to retrieve the state of the entire mesh by using mesh instead o
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--context <string></code></td>
|
||||
<td></td>
|
||||
<td>The name of the kubeconfig context to use (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--istioNamespace <string></code></td>
|
||||
<td><code>-i</code></td>
|
||||
<td>Istio system namespace (default `istio-system`)</td>
|
||||
|
|
@ -1269,7 +1339,7 @@ It is also able to retrieve the state of the entire mesh by using mesh instead o
|
|||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td><code>-c</code></td>
|
||||
<td>Kubernetes configuration file (default `$KUBECONFIG else $HOME/.kube/config`)</td>
|
||||
<td>Kubernetes configuration file (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--log_as_json</code></td>
|
||||
|
|
@ -1328,7 +1398,7 @@ It is also able to retrieve the state of the entire mesh by using mesh instead o
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="istioctl proxy-config Examples">Examples</h3>
|
||||
<h3 id="istioctl-proxy-config Examples">Examples</h3>
|
||||
<pre class="language-bash"><code># Retrieve all config for productpage-v1-bb8d5cbc7-k7qbm pod from the endpoint proxy
|
||||
istioctl proxy-config endpoint productpage-v1-bb8d5cbc7-k7qbm
|
||||
|
||||
|
|
@ -1341,7 +1411,7 @@ istioctl proxy-config pilot mesh ads
|
|||
# Retrieve static config for productpage-v1-bb8d5cbc7-k7qbm pod in the application namespace from the endpoint proxy
|
||||
istioctl proxy-config endpoint -n application productpage-v1-bb8d5cbc7-k7qbm static
|
||||
</code></pre>
|
||||
<h2 id="istioctl register">istioctl register</h2>
|
||||
<h2 id="istioctl-register">istioctl register</h2>
|
||||
<p>Registers a service instance (e.g. VM) joining the mesh</p>
|
||||
<pre class="language-bash"><code>istioctl register <svcname> <ip> [name1:]port1 [name2:]port2 ... [flags]
|
||||
</code></pre>
|
||||
|
|
@ -1358,6 +1428,11 @@ istioctl proxy-config endpoint -n application productpage-v1-bb8d5cbc7-k7qbm sta
|
|||
<td>List of string annotations to apply if creating a service/endpoint; e.g. -a foo=bar,test,x=y (default `[]`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--context <string></code></td>
|
||||
<td></td>
|
||||
<td>The name of the kubeconfig context to use (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--istioNamespace <string></code></td>
|
||||
<td><code>-i</code></td>
|
||||
<td>Istio system namespace (default `istio-system`)</td>
|
||||
|
|
@ -1365,7 +1440,7 @@ istioctl proxy-config endpoint -n application productpage-v1-bb8d5cbc7-k7qbm sta
|
|||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td><code>-c</code></td>
|
||||
<td>Kubernetes configuration file (default `$KUBECONFIG else $HOME/.kube/config`)</td>
|
||||
<td>Kubernetes configuration file (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--labels <stringSlice></code></td>
|
||||
|
|
@ -1434,7 +1509,7 @@ istioctl proxy-config endpoint -n application productpage-v1-bb8d5cbc7-k7qbm sta
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="istioctl replace">istioctl replace</h2>
|
||||
<h2 id="istioctl-replace">istioctl replace</h2>
|
||||
<p>Replace existing policies and rules</p>
|
||||
<pre class="language-bash"><code>istioctl replace [flags]
|
||||
</code></pre>
|
||||
|
|
@ -1446,6 +1521,11 @@ istioctl proxy-config endpoint -n application productpage-v1-bb8d5cbc7-k7qbm sta
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--context <string></code></td>
|
||||
<td></td>
|
||||
<td>The name of the kubeconfig context to use (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--file <string></code></td>
|
||||
<td><code>-f</code></td>
|
||||
<td>Input file with the content of the configuration objects (if not set, command reads from the standard input) (default ``)</td>
|
||||
|
|
@ -1458,7 +1538,7 @@ istioctl proxy-config endpoint -n application productpage-v1-bb8d5cbc7-k7qbm sta
|
|||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td><code>-c</code></td>
|
||||
<td>Kubernetes configuration file (default `$KUBECONFIG else $HOME/.kube/config`)</td>
|
||||
<td>Kubernetes configuration file (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--log_as_json</code></td>
|
||||
|
|
@ -1517,10 +1597,10 @@ istioctl proxy-config endpoint -n application productpage-v1-bb8d5cbc7-k7qbm sta
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="istioctl replace Examples">Examples</h3>
|
||||
<h3 id="istioctl-replace Examples">Examples</h3>
|
||||
<pre class="language-bash"><code>istioctl replace -f example-routing.yaml
|
||||
</code></pre>
|
||||
<h2 id="istioctl version">istioctl version</h2>
|
||||
<h2 id="istioctl-version">istioctl version</h2>
|
||||
<p>Prints out build version information</p>
|
||||
<pre class="language-bash"><code>istioctl version [flags]
|
||||
</code></pre>
|
||||
|
|
@ -1532,6 +1612,11 @@ istioctl proxy-config endpoint -n application productpage-v1-bb8d5cbc7-k7qbm sta
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--context <string></code></td>
|
||||
<td></td>
|
||||
<td>The name of the kubeconfig context to use (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--istioNamespace <string></code></td>
|
||||
<td><code>-i</code></td>
|
||||
<td>Istio system namespace (default `istio-system`)</td>
|
||||
|
|
@ -1539,7 +1624,7 @@ istioctl proxy-config endpoint -n application productpage-v1-bb8d5cbc7-k7qbm sta
|
|||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td><code>-c</code></td>
|
||||
<td>Kubernetes configuration file (default `$KUBECONFIG else $HOME/.kube/config`)</td>
|
||||
<td>Kubernetes configuration file (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--log_as_json</code></td>
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ number_of_entries: 5
|
|||
<p>This command lets you interact with a running instance of
|
||||
Mixer. Note that you need a pretty good understanding of Mixer's
|
||||
API in order to use this command.</p>
|
||||
<h2 id="mixc check">mixc check</h2>
|
||||
<h2 id="mixc-check">mixc check</h2>
|
||||
<p>The Check method is used to perform precondition checks and quota allocations. Mixer
|
||||
expects a set of attributes as input, which it uses, along with
|
||||
its configuration, to determine which adapters to invoke and with
|
||||
|
|
@ -98,7 +98,7 @@ which parameters in order to perform the checks and allocations.</p>
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="mixc report">mixc report</h2>
|
||||
<h2 id="mixc-report">mixc report</h2>
|
||||
<p>The Report method is used to produce telemetry. Mixer
|
||||
expects a set of attributes as input, which it uses, along with
|
||||
its configuration, to determine which adapters to invoke and with
|
||||
|
|
@ -184,7 +184,7 @@ which parameters in order to output the telemetry.</p>
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="mixc version">mixc version</h2>
|
||||
<h2 id="mixc-version">mixc version</h2>
|
||||
<p>Prints out build version information</p>
|
||||
<pre class="language-bash"><code>mixc version [flags]
|
||||
</code></pre>
|
||||
|
|
|
|||
|
|
@ -6,21 +6,21 @@ number_of_entries: 9
|
|||
---
|
||||
<p>Mixer is Istio's point of integration with infrastructure backends and is the
|
||||
nexus for policy evaluation and telemetry reporting.</p>
|
||||
<h2 id="mixs crd">mixs crd</h2>
|
||||
<h2 id="mixs-crd">mixs crd</h2>
|
||||
<p>CRDs (CustomResourceDefinition) available in Mixer</p>
|
||||
<h2 id="mixs crd adapter">mixs crd adapter</h2>
|
||||
<h2 id="mixs-crd-adapter">mixs crd adapter</h2>
|
||||
<p>List CRDs for available adapters</p>
|
||||
<pre class="language-bash"><code>mixs crd adapter [flags]
|
||||
</code></pre>
|
||||
<h2 id="mixs crd all">mixs crd all</h2>
|
||||
<h2 id="mixs-crd-all">mixs crd all</h2>
|
||||
<p>List all CRDs</p>
|
||||
<pre class="language-bash"><code>mixs crd all [flags]
|
||||
</code></pre>
|
||||
<h2 id="mixs crd instance">mixs crd instance</h2>
|
||||
<h2 id="mixs-crd-instance">mixs crd instance</h2>
|
||||
<p>List CRDs for available instance kinds (mesh functions)</p>
|
||||
<pre class="language-bash"><code>mixs crd instance [flags]
|
||||
</code></pre>
|
||||
<h2 id="mixs probe">mixs probe</h2>
|
||||
<h2 id="mixs-probe">mixs probe</h2>
|
||||
<p>Check the liveness or readiness of a locally-running server</p>
|
||||
<pre class="language-bash"><code>mixs probe [flags]
|
||||
</code></pre>
|
||||
|
|
@ -76,7 +76,7 @@ nexus for policy evaluation and telemetry reporting.</p>
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="mixs server">mixs server</h2>
|
||||
<h2 id="mixs-server">mixs server</h2>
|
||||
<p>Starts Mixer as a server</p>
|
||||
<pre class="language-bash"><code>mixs server [flags]
|
||||
</code></pre>
|
||||
|
|
@ -234,7 +234,7 @@ nexus for policy evaluation and telemetry reporting.</p>
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="mixs version">mixs version</h2>
|
||||
<h2 id="mixs-version">mixs version</h2>
|
||||
<p>Prints out build version information</p>
|
||||
<pre class="language-bash"><code>mixs version [flags]
|
||||
</code></pre>
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@ number_of_entries: 3
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="node_agent version">node_agent version</h2>
|
||||
<h2 id="node_agent-version">node_agent version</h2>
|
||||
<p>Prints out build version information</p>
|
||||
<pre class="language-bash"><code>node_agent version [flags]
|
||||
</code></pre>
|
||||
|
|
|
|||
|
|
@ -49,7 +49,7 @@ number_of_entries: 5
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="pilot-agent debug">pilot-agent debug</h2>
|
||||
<h2 id="pilot-agent-debug">pilot-agent debug</h2>
|
||||
<p>Debug local envoy</p>
|
||||
<pre class="language-bash"><code>pilot-agent debug <configuration-type> [flags]
|
||||
</code></pre>
|
||||
|
|
@ -97,7 +97,7 @@ number_of_entries: 5
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="pilot-agent proxy">pilot-agent proxy</h2>
|
||||
<h2 id="pilot-agent-proxy">pilot-agent proxy</h2>
|
||||
<p>Envoy proxy agent</p>
|
||||
<pre class="language-bash"><code>pilot-agent proxy [flags]
|
||||
</code></pre>
|
||||
|
|
@ -221,7 +221,7 @@ number_of_entries: 5
|
|||
</tr>
|
||||
<tr>
|
||||
<td><code>--serviceregistry <string></code></td>
|
||||
<td>Select the platform for service registry, options are {Kubernetes, Consul, Eureka, CloudFoundry, Mock} (default `Kubernetes`)</td>
|
||||
<td>Select the platform for service registry, options are {Kubernetes, Consul, Eureka, CloudFoundry, Mock, Config} (default `Kubernetes`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--statsdUdpAddress <string></code></td>
|
||||
|
|
@ -237,7 +237,7 @@ number_of_entries: 5
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="pilot-agent version">pilot-agent version</h2>
|
||||
<h2 id="pilot-agent-version">pilot-agent version</h2>
|
||||
<p>Prints out build version information</p>
|
||||
<pre class="language-bash"><code>pilot-agent version [flags]
|
||||
</code></pre>
|
||||
|
|
|
|||
|
|
@ -57,7 +57,7 @@ number_of_entries: 5
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="pilot-discovery debug">pilot-discovery debug</h2>
|
||||
<h2 id="pilot-discovery-debug">pilot-discovery debug</h2>
|
||||
<p>Retrieve the configuration for the specified proxy</p>
|
||||
<pre class="language-bash"><code>pilot-discovery debug <proxyID> <configuration-type> [flags]
|
||||
</code></pre>
|
||||
|
|
@ -113,7 +113,7 @@ number_of_entries: 5
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="pilot-discovery discovery">pilot-discovery discovery</h2>
|
||||
<h2 id="pilot-discovery-discovery">pilot-discovery discovery</h2>
|
||||
<p>Start Istio proxy discovery service</p>
|
||||
<pre class="language-bash"><code>pilot-discovery discovery [flags]
|
||||
</code></pre>
|
||||
|
|
@ -195,6 +195,11 @@ number_of_entries: 5
|
|||
<td>Discovery service grpc address (default `:15010`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--httpAddr <string></code></td>
|
||||
<td></td>
|
||||
<td>Discovery service HTTP address (default `:8080`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td></td>
|
||||
<td>Use a Kubernetes configuration file instead of in-cluster configuration (default ``)</td>
|
||||
|
|
@ -250,9 +255,9 @@ number_of_entries: 5
|
|||
<td>File name for Istio mesh configuration. If not specified, a default mesh will be used. (default `/etc/istio/config/mesh`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--monitoringPort <int></code></td>
|
||||
<td><code>--monitoringAddr <string></code></td>
|
||||
<td></td>
|
||||
<td>HTTP port to use for the exposing pilot self-monitoring information (default `9093`)</td>
|
||||
<td>HTTP address to use for the exposing pilot self-monitoring information (default `:9093`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace <string></code></td>
|
||||
|
|
@ -260,11 +265,6 @@ number_of_entries: 5
|
|||
<td>Select a namespace where the controller resides. If not set, uses ${POD_NAMESPACE} environment variable (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--port <int></code></td>
|
||||
<td></td>
|
||||
<td>Discovery service port (default `8080`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--profile</code></td>
|
||||
<td></td>
|
||||
<td>Enable profiling via web interface host:port/debug/pprof </td>
|
||||
|
|
@ -272,7 +272,7 @@ number_of_entries: 5
|
|||
<tr>
|
||||
<td><code>--registries <stringSlice></code></td>
|
||||
<td></td>
|
||||
<td>Comma separated list of platform service registries to read from (choose one or more from {Kubernetes, Consul, Eureka, CloudFoundry, Mock}) (default `[Kubernetes]`)</td>
|
||||
<td>Comma separated list of platform service registries to read from (choose one or more from {Kubernetes, Consul, Eureka, CloudFoundry, Mock, Config}) (default `[Kubernetes]`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--resync <duration></code></td>
|
||||
|
|
@ -291,7 +291,7 @@ number_of_entries: 5
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="pilot-discovery version">pilot-discovery version</h2>
|
||||
<h2 id="pilot-discovery-version">pilot-discovery version</h2>
|
||||
<p>Prints out build version information</p>
|
||||
<pre class="language-bash"><code>pilot-discovery version [flags]
|
||||
</code></pre>
|
||||
|
|
|
|||
|
|
@ -95,7 +95,7 @@ number_of_entries: 4
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="sidecar-injector probe">sidecar-injector probe</h2>
|
||||
<h2 id="sidecar-injector-probe">sidecar-injector probe</h2>
|
||||
<p>Check the liveness or readiness of a locally-running server</p>
|
||||
<pre class="language-bash"><code>sidecar-injector probe [flags]
|
||||
</code></pre>
|
||||
|
|
@ -195,7 +195,7 @@ number_of_entries: 4
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="sidecar-injector version">sidecar-injector version</h2>
|
||||
<h2 id="sidecar-injector-version">sidecar-injector version</h2>
|
||||
<p>Prints out build version information</p>
|
||||
<pre class="language-bash"><code>sidecar-injector version [flags]
|
||||
</code></pre>
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load Diff
|
|
@ -103,7 +103,7 @@ spec:
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="AccessRule.services">
|
||||
<tr id="AccessRule-services">
|
||||
<td><code>services</code></td>
|
||||
<td><code>string[]</code></td>
|
||||
<td>
|
||||
|
|
@ -116,7 +116,7 @@ If set to [“*”], it refers to all services in the namespace.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="AccessRule.paths">
|
||||
<tr id="AccessRule-paths">
|
||||
<td><code>paths</code></td>
|
||||
<td><code>string[]</code></td>
|
||||
<td>
|
||||
|
|
@ -131,7 +131,7 @@ If not specified, it applies to any path.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="AccessRule.methods">
|
||||
<tr id="AccessRule-methods">
|
||||
<td><code>methods</code></td>
|
||||
<td><code>string[]</code></td>
|
||||
<td>
|
||||
|
|
@ -141,9 +141,9 @@ If set to [“*”] or not specified, it applies to any method.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="AccessRule.constraints">
|
||||
<tr id="AccessRule-constraints">
|
||||
<td><code>constraints</code></td>
|
||||
<td><code><a href="#AccessRule.Constraint">AccessRule.Constraint[]</a></code></td>
|
||||
<td><code><a href="#AccessRule-Constraint">AccessRule.Constraint[]</a></code></td>
|
||||
<td>
|
||||
<p>Optional. Extra constraints in the ServiceRole specification.
|
||||
The above ServiceRole examples shows an example of constraint “version”.</p>
|
||||
|
|
@ -153,7 +153,7 @@ The above ServiceRole examples shows an example of constraint “version&rdq
|
|||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="AccessRule.Constraint">AccessRule.Constraint</h2>
|
||||
<h2 id="AccessRule-Constraint">AccessRule.Constraint</h2>
|
||||
<section>
|
||||
<p>Definition of a custom constraint. The key of a custom constraint must match
|
||||
one of the “properties” in the “action” part of the “authorization” template
|
||||
|
|
@ -168,7 +168,7 @@ one of the “properties” in the “action” part of the &ldq
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="AccessRule.Constraint.key">
|
||||
<tr id="AccessRule-Constraint-key">
|
||||
<td><code>key</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -176,7 +176,7 @@ one of the “properties” in the “action” part of the &ldq
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="AccessRule.Constraint.values">
|
||||
<tr id="AccessRule-Constraint-values">
|
||||
<td><code>values</code></td>
|
||||
<td><code>string[]</code></td>
|
||||
<td>
|
||||
|
|
@ -222,26 +222,26 @@ spec:
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="RbacConfig.mode">
|
||||
<tr id="RbacConfig-mode">
|
||||
<td><code>mode</code></td>
|
||||
<td><code><a href="#RbacConfig.Mode">RbacConfig.Mode</a></code></td>
|
||||
<td><code><a href="#RbacConfig-Mode">RbacConfig.Mode</a></code></td>
|
||||
<td>
|
||||
<p>Istio RBAC mode.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="RbacConfig.inclusion">
|
||||
<tr id="RbacConfig-inclusion">
|
||||
<td><code>inclusion</code></td>
|
||||
<td><code><a href="#RbacConfig.Target">RbacConfig.Target</a></code></td>
|
||||
<td><code><a href="#RbacConfig-Target">RbacConfig.Target</a></code></td>
|
||||
<td>
|
||||
<p>A list of services or namespaces that should be enforced by Istio RBAC policies. Note: This field have
|
||||
effect only when mode is ON<em>WITH</em>INCLUSION and will be ignored for any other modes.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="RbacConfig.exclusion">
|
||||
<tr id="RbacConfig-exclusion">
|
||||
<td><code>exclusion</code></td>
|
||||
<td><code><a href="#RbacConfig.Target">RbacConfig.Target</a></code></td>
|
||||
<td><code><a href="#RbacConfig-Target">RbacConfig.Target</a></code></td>
|
||||
<td>
|
||||
<p>A list of services or namespaces that should not be enforced by Istio RBAC policies. Note: This field have
|
||||
effect only when mode is ON<em>WITH</em>EXCLUSION and will be ignored for any other modes.</p>
|
||||
|
|
@ -251,7 +251,7 @@ effect only when mode is ON<em>WITH</em>EXCLUSION and will be ignored for any ot
|
|||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="RbacConfig.Mode">RbacConfig.Mode</h2>
|
||||
<h2 id="RbacConfig-Mode">RbacConfig.Mode</h2>
|
||||
<section>
|
||||
<table class="enum-values">
|
||||
<thead>
|
||||
|
|
@ -261,7 +261,7 @@ effect only when mode is ON<em>WITH</em>EXCLUSION and will be ignored for any ot
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="RbacConfig.Mode.OFF">
|
||||
<tr id="RbacConfig-Mode-OFF">
|
||||
<td><code>OFF</code></td>
|
||||
<td>
|
||||
<p>Disable Istio RBAC completely, any other config in RbacConfig will be ignored and Istio RBAC policies
|
||||
|
|
@ -269,14 +269,14 @@ will not be enforced.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="RbacConfig.Mode.ON">
|
||||
<tr id="RbacConfig-Mode-ON">
|
||||
<td><code>ON</code></td>
|
||||
<td>
|
||||
<p>Enable Istio RBAC for all services and namespaces.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="RbacConfig.Mode.ON_WITH_INCLUSION">
|
||||
<tr id="RbacConfig-Mode-ON_WITH_INCLUSION">
|
||||
<td><code>ON_WITH_INCLUSION</code></td>
|
||||
<td>
|
||||
<p>Enable Istio RBAC only for services and namespaces specified in the inclusion field. Any other
|
||||
|
|
@ -284,7 +284,7 @@ services and namespaces not in the inclusion field will not be enforced by Istio
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="RbacConfig.Mode.ON_WITH_EXCLUSION">
|
||||
<tr id="RbacConfig-Mode-ON_WITH_EXCLUSION">
|
||||
<td><code>ON_WITH_EXCLUSION</code></td>
|
||||
<td>
|
||||
<p>Enable Istio RBAC for all services and namespaces except those specified in the exclusion field. Any other
|
||||
|
|
@ -295,7 +295,7 @@ services and namespaces not in the exclusion field will be enforced by Istio RBA
|
|||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="RbacConfig.Target">RbacConfig.Target</h2>
|
||||
<h2 id="RbacConfig-Target">RbacConfig.Target</h2>
|
||||
<section>
|
||||
<p>Target defines a list of services or namespaces.</p>
|
||||
|
||||
|
|
@ -308,7 +308,7 @@ services and namespaces not in the exclusion field will be enforced by Istio RBA
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="RbacConfig.Target.services">
|
||||
<tr id="RbacConfig-Target-services">
|
||||
<td><code>services</code></td>
|
||||
<td><code>string[]</code></td>
|
||||
<td>
|
||||
|
|
@ -316,7 +316,7 @@ services and namespaces not in the exclusion field will be enforced by Istio RBA
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="RbacConfig.Target.namespaces">
|
||||
<tr id="RbacConfig-Target-namespaces">
|
||||
<td><code>namespaces</code></td>
|
||||
<td><code>string[]</code></td>
|
||||
<td>
|
||||
|
|
@ -340,7 +340,7 @@ services and namespaces not in the exclusion field will be enforced by Istio RBA
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="RoleRef.kind">
|
||||
<tr id="RoleRef-kind">
|
||||
<td><code>kind</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -349,7 +349,7 @@ Currently, “ServiceRole” is the only supported value for “kind
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="RoleRef.name">
|
||||
<tr id="RoleRef-name">
|
||||
<td><code>name</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -377,7 +377,7 @@ of the ServiceRole is specified in “metadata” section of the Service
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="ServiceRole.rules">
|
||||
<tr id="ServiceRole-rules">
|
||||
<td><code>rules</code></td>
|
||||
<td><code><a href="#AccessRule">AccessRule[]</a></code></td>
|
||||
<td>
|
||||
|
|
@ -404,7 +404,7 @@ object.</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="ServiceRoleBinding.subjects">
|
||||
<tr id="ServiceRoleBinding-subjects">
|
||||
<td><code>subjects</code></td>
|
||||
<td><code><a href="#Subject">Subject[]</a></code></td>
|
||||
<td>
|
||||
|
|
@ -412,7 +412,7 @@ object.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="ServiceRoleBinding.roleRef">
|
||||
<tr id="ServiceRoleBinding-roleRef">
|
||||
<td><code>roleRef</code></td>
|
||||
<td><code><a href="#RoleRef">RoleRef</a></code></td>
|
||||
<td>
|
||||
|
|
@ -439,7 +439,7 @@ the “properties” in the “subject” part of the “aut
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="Subject.user">
|
||||
<tr id="Subject-user">
|
||||
<td><code>user</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -447,7 +447,7 @@ the “properties” in the “subject” part of the “aut
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Subject.group">
|
||||
<tr id="Subject-group">
|
||||
<td><code>group</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -455,7 +455,7 @@ the “properties” in the “subject” part of the “aut
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Subject.properties">
|
||||
<tr id="Subject-properties">
|
||||
<td><code>properties</code></td>
|
||||
<td><code>map<string, string></code></td>
|
||||
<td>
|
||||
|
|
|
|||
|
|
@ -61,13 +61,13 @@ for more details.</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="CircuitBreaker.simple_cb" class="oneof oneof-start">
|
||||
<tr id="CircuitBreaker-simple_cb" class="oneof oneof-start">
|
||||
<td><code>simpleCb</code></td>
|
||||
<td><code><a href="#CircuitBreaker.SimpleCircuitBreakerPolicy">CircuitBreaker.SimpleCircuitBreakerPolicy (oneof)</a></code></td>
|
||||
<td><code><a href="#CircuitBreaker-SimpleCircuitBreakerPolicy">CircuitBreaker.SimpleCircuitBreakerPolicy (oneof)</a></code></td>
|
||||
<td>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="CircuitBreaker.custom" class="oneof">
|
||||
<tr id="CircuitBreaker-custom" class="oneof">
|
||||
<td><code>custom</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#any">google.protobuf.Any (oneof)</a></code></td>
|
||||
<td>
|
||||
|
|
@ -78,7 +78,7 @@ for more details.</p>
|
|||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="CircuitBreaker.SimpleCircuitBreakerPolicy">CircuitBreaker.SimpleCircuitBreakerPolicy</h2>
|
||||
<h2 id="CircuitBreaker-SimpleCircuitBreakerPolicy">CircuitBreaker.SimpleCircuitBreakerPolicy</h2>
|
||||
<section>
|
||||
<p>A simple circuit breaker can be set based on a number of criteria such as
|
||||
connection and request limits. For example, the following destination
|
||||
|
|
@ -131,7 +131,7 @@ spec:
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="CircuitBreaker.SimpleCircuitBreakerPolicy.max_connections">
|
||||
<tr id="CircuitBreaker-SimpleCircuitBreakerPolicy-max_connections">
|
||||
<td><code>maxConnections</code></td>
|
||||
<td><code>int32</code></td>
|
||||
<td>
|
||||
|
|
@ -139,7 +139,7 @@ spec:
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="CircuitBreaker.SimpleCircuitBreakerPolicy.http_max_pending_requests">
|
||||
<tr id="CircuitBreaker-SimpleCircuitBreakerPolicy-http_max_pending_requests">
|
||||
<td><code>httpMaxPendingRequests</code></td>
|
||||
<td><code>int32</code></td>
|
||||
<td>
|
||||
|
|
@ -147,7 +147,7 @@ spec:
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="CircuitBreaker.SimpleCircuitBreakerPolicy.http_max_requests">
|
||||
<tr id="CircuitBreaker-SimpleCircuitBreakerPolicy-http_max_requests">
|
||||
<td><code>httpMaxRequests</code></td>
|
||||
<td><code>int32</code></td>
|
||||
<td>
|
||||
|
|
@ -155,7 +155,7 @@ spec:
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="CircuitBreaker.SimpleCircuitBreakerPolicy.sleep_window">
|
||||
<tr id="CircuitBreaker-SimpleCircuitBreakerPolicy-sleep_window">
|
||||
<td><code>sleepWindow</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#duration">google.protobuf.Duration</a></code></td>
|
||||
<td>
|
||||
|
|
@ -164,7 +164,7 @@ BE >=1ms. Default is 30s.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="CircuitBreaker.SimpleCircuitBreakerPolicy.http_consecutive_errors">
|
||||
<tr id="CircuitBreaker-SimpleCircuitBreakerPolicy-http_consecutive_errors">
|
||||
<td><code>httpConsecutiveErrors</code></td>
|
||||
<td><code>int32</code></td>
|
||||
<td>
|
||||
|
|
@ -172,7 +172,7 @@ BE >=1ms. Default is 30s.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="CircuitBreaker.SimpleCircuitBreakerPolicy.http_detection_interval">
|
||||
<tr id="CircuitBreaker-SimpleCircuitBreakerPolicy-http_detection_interval">
|
||||
<td><code>httpDetectionInterval</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#duration">google.protobuf.Duration</a></code></td>
|
||||
<td>
|
||||
|
|
@ -181,7 +181,7 @@ BE >=1ms. Default is 30s.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="CircuitBreaker.SimpleCircuitBreakerPolicy.http_max_requests_per_connection">
|
||||
<tr id="CircuitBreaker-SimpleCircuitBreakerPolicy-http_max_requests_per_connection">
|
||||
<td><code>httpMaxRequestsPerConnection</code></td>
|
||||
<td><code>int32</code></td>
|
||||
<td>
|
||||
|
|
@ -190,7 +190,7 @@ parameter to 1 disables keep alive.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="CircuitBreaker.SimpleCircuitBreakerPolicy.http_max_ejection_percent">
|
||||
<tr id="CircuitBreaker-SimpleCircuitBreakerPolicy-http_max_ejection_percent">
|
||||
<td><code>httpMaxEjectionPercent</code></td>
|
||||
<td><code>int32</code></td>
|
||||
<td>
|
||||
|
|
@ -200,7 +200,7 @@ service that can be ejected by the circuit breaker. Defaults to
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="CircuitBreaker.SimpleCircuitBreakerPolicy.http_max_retries">
|
||||
<tr id="CircuitBreaker-SimpleCircuitBreakerPolicy-http_max_retries">
|
||||
<td><code>httpMaxRetries</code></td>
|
||||
<td><code>int32</code></td>
|
||||
<td>
|
||||
|
|
@ -253,7 +253,7 @@ spec:
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="CorsPolicy.allow_origin">
|
||||
<tr id="CorsPolicy-allow_origin">
|
||||
<td><code>allowOrigin</code></td>
|
||||
<td><code>string[]</code></td>
|
||||
<td>
|
||||
|
|
@ -263,7 +263,7 @@ all origins.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="CorsPolicy.allow_methods">
|
||||
<tr id="CorsPolicy-allow_methods">
|
||||
<td><code>allowMethods</code></td>
|
||||
<td><code>string[]</code></td>
|
||||
<td>
|
||||
|
|
@ -272,7 +272,7 @@ be serialized into the Access-Control-Allow-Methods header.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="CorsPolicy.allow_headers">
|
||||
<tr id="CorsPolicy-allow_headers">
|
||||
<td><code>allowHeaders</code></td>
|
||||
<td><code>string[]</code></td>
|
||||
<td>
|
||||
|
|
@ -281,7 +281,7 @@ resource. Serialized to Access-Control-Allow-Methods header.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="CorsPolicy.expose_headers">
|
||||
<tr id="CorsPolicy-expose_headers">
|
||||
<td><code>exposeHeaders</code></td>
|
||||
<td><code>string[]</code></td>
|
||||
<td>
|
||||
|
|
@ -290,7 +290,7 @@ access. Serialized into Access-Control-Expose-Headers header.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="CorsPolicy.max_age">
|
||||
<tr id="CorsPolicy-max_age">
|
||||
<td><code>maxAge</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#duration">google.protobuf.Duration</a></code></td>
|
||||
<td>
|
||||
|
|
@ -299,7 +299,7 @@ cached. Translates to the Access-Control-Max-Age header.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="CorsPolicy.allow_credentials">
|
||||
<tr id="CorsPolicy-allow_credentials">
|
||||
<td><code>allowCredentials</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#boolvalue">google.protobuf.BoolValue</a></code></td>
|
||||
<td>
|
||||
|
|
@ -371,7 +371,7 @@ service version indicated in the destination policy.</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="DestinationPolicy.destination">
|
||||
<tr id="DestinationPolicy-destination">
|
||||
<td><code>destination</code></td>
|
||||
<td><code><a href="#IstioService">IstioService</a></code></td>
|
||||
<td>
|
||||
|
|
@ -380,7 +380,7 @@ with this policy.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="DestinationPolicy.source">
|
||||
<tr id="DestinationPolicy-source">
|
||||
<td><code>source</code></td>
|
||||
<td><code><a href="#IstioService">IstioService</a></code></td>
|
||||
<td>
|
||||
|
|
@ -389,7 +389,7 @@ with this policy.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="DestinationPolicy.load_balancing">
|
||||
<tr id="DestinationPolicy-load_balancing">
|
||||
<td><code>loadBalancing</code></td>
|
||||
<td><code><a href="#LoadBalancing">LoadBalancing</a></code></td>
|
||||
<td>
|
||||
|
|
@ -397,7 +397,7 @@ with this policy.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="DestinationPolicy.circuit_breaker">
|
||||
<tr id="DestinationPolicy-circuit_breaker">
|
||||
<td><code>circuitBreaker</code></td>
|
||||
<td><code><a href="#CircuitBreaker">CircuitBreaker</a></code></td>
|
||||
<td>
|
||||
|
|
@ -405,7 +405,7 @@ with this policy.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="DestinationPolicy.custom">
|
||||
<tr id="DestinationPolicy-custom">
|
||||
<td><code>custom</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#any">google.protobuf.Any</a></code></td>
|
||||
<td>
|
||||
|
|
@ -449,7 +449,7 @@ spec:
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="DestinationWeight.destination">
|
||||
<tr id="DestinationWeight-destination">
|
||||
<td><code>destination</code></td>
|
||||
<td><code><a href="#IstioService">IstioService</a></code></td>
|
||||
<td>
|
||||
|
|
@ -458,7 +458,7 @@ specified, the value is inherited from the parent route rule.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="DestinationWeight.labels">
|
||||
<tr id="DestinationWeight-labels">
|
||||
<td><code>labels</code></td>
|
||||
<td><code>map<string, string></code></td>
|
||||
<td>
|
||||
|
|
@ -468,7 +468,7 @@ in golang protobuf library (see https://github.com/golang/protobuf/pull/208) &nd
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="DestinationWeight.weight">
|
||||
<tr id="DestinationWeight-weight">
|
||||
<td><code>weight</code></td>
|
||||
<td><code>int32</code></td>
|
||||
<td>
|
||||
|
|
@ -535,7 +535,7 @@ spec:
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="EgressRule.destination">
|
||||
<tr id="EgressRule-destination">
|
||||
<td><code>destination</code></td>
|
||||
<td><code><a href="#IstioService">IstioService</a></code></td>
|
||||
<td>
|
||||
|
|
@ -556,15 +556,15 @@ domain of form “</em>-bar.foo.com” will match “baz-bar.foo.com” but not
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="EgressRule.ports">
|
||||
<tr id="EgressRule-ports">
|
||||
<td><code>ports</code></td>
|
||||
<td><code><a href="#EgressRule.Port">EgressRule.Port[]</a></code></td>
|
||||
<td><code><a href="#EgressRule-Port">EgressRule.Port[]</a></code></td>
|
||||
<td>
|
||||
<p>REQUIRED: list of ports on which the external service is available.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="EgressRule.use_egress_proxy">
|
||||
<tr id="EgressRule-use_egress_proxy">
|
||||
<td><code>useEgressProxy</code></td>
|
||||
<td><code>bool</code></td>
|
||||
<td>
|
||||
|
|
@ -579,7 +579,7 @@ These dedicated egress nodes could then be more closely monitored for security v
|
|||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="EgressRule.Port">EgressRule.Port</h2>
|
||||
<h2 id="EgressRule-Port">EgressRule.Port</h2>
|
||||
<section>
|
||||
<p>Port describes the properties of a specific TCP port of an external service.</p>
|
||||
|
||||
|
|
@ -592,7 +592,7 @@ These dedicated egress nodes could then be more closely monitored for security v
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="EgressRule.Port.port">
|
||||
<tr id="EgressRule-Port-port">
|
||||
<td><code>port</code></td>
|
||||
<td><code>int32</code></td>
|
||||
<td>
|
||||
|
|
@ -600,7 +600,7 @@ These dedicated egress nodes could then be more closely monitored for security v
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="EgressRule.Port.protocol">
|
||||
<tr id="EgressRule-Port-protocol">
|
||||
<td><code>protocol</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -632,18 +632,18 @@ both are specified simultaneously.</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="HTTPFaultInjection.delay">
|
||||
<tr id="HTTPFaultInjection-delay">
|
||||
<td><code>delay</code></td>
|
||||
<td><code><a href="#HTTPFaultInjection.Delay">HTTPFaultInjection.Delay</a></code></td>
|
||||
<td><code><a href="#HTTPFaultInjection-Delay">HTTPFaultInjection.Delay</a></code></td>
|
||||
<td>
|
||||
<p>Delay requests before forwarding, emulating various failures such as
|
||||
network issues, overloaded upstream service, etc.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="HTTPFaultInjection.abort">
|
||||
<tr id="HTTPFaultInjection-abort">
|
||||
<td><code>abort</code></td>
|
||||
<td><code><a href="#HTTPFaultInjection.Abort">HTTPFaultInjection.Abort</a></code></td>
|
||||
<td><code><a href="#HTTPFaultInjection-Abort">HTTPFaultInjection.Abort</a></code></td>
|
||||
<td>
|
||||
<p>Abort Http request attempts and return error codes back to downstream
|
||||
service, giving the impression that the upstream service is faulty.</p>
|
||||
|
|
@ -653,7 +653,7 @@ service, giving the impression that the upstream service is faulty.</p>
|
|||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="HTTPFaultInjection.Abort">HTTPFaultInjection.Abort</h2>
|
||||
<h2 id="HTTPFaultInjection-Abort">HTTPFaultInjection.Abort</h2>
|
||||
<section>
|
||||
<p>Abort specification is used to prematurely abort a request with a
|
||||
pre-specified error code. The following example will return an HTTP
|
||||
|
|
@ -687,7 +687,7 @@ not specified, all requests are aborted.</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="HTTPFaultInjection.Abort.percent">
|
||||
<tr id="HTTPFaultInjection-Abort-percent">
|
||||
<td><code>percent</code></td>
|
||||
<td><code>float</code></td>
|
||||
<td>
|
||||
|
|
@ -695,19 +695,19 @@ not specified, all requests are aborted.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="HTTPFaultInjection.Abort.grpc_status" class="oneof oneof-start">
|
||||
<tr id="HTTPFaultInjection-Abort-grpc_status" class="oneof oneof-start">
|
||||
<td><code>grpcStatus</code></td>
|
||||
<td><code>string (oneof)</code></td>
|
||||
<td>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="HTTPFaultInjection.Abort.http2_error" class="oneof">
|
||||
<tr id="HTTPFaultInjection-Abort-http2_error" class="oneof">
|
||||
<td><code>http2Error</code></td>
|
||||
<td><code>string (oneof)</code></td>
|
||||
<td>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="HTTPFaultInjection.Abort.http_status" class="oneof">
|
||||
<tr id="HTTPFaultInjection-Abort-http_status" class="oneof">
|
||||
<td><code>httpStatus</code></td>
|
||||
<td><code>int32 (oneof)</code></td>
|
||||
<td>
|
||||
|
|
@ -715,7 +715,7 @@ not specified, all requests are aborted.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="HTTPFaultInjection.Abort.override_header_name">
|
||||
<tr id="HTTPFaultInjection-Abort-override_header_name">
|
||||
<td><code>overrideHeaderName</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -727,7 +727,7 @@ TODO: The semantics and syntax of the headers is undefined. –)</p>
|
|||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="HTTPFaultInjection.Delay">HTTPFaultInjection.Delay</h2>
|
||||
<h2 id="HTTPFaultInjection-Delay">HTTPFaultInjection.Delay</h2>
|
||||
<section>
|
||||
<p>Delay specification is used to inject latency into the request
|
||||
forwarding path. The following example will introduce a 5 second delay
|
||||
|
|
@ -762,7 +762,7 @@ unspecified, all request will be delayed.</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="HTTPFaultInjection.Delay.percent">
|
||||
<tr id="HTTPFaultInjection-Delay-percent">
|
||||
<td><code>percent</code></td>
|
||||
<td><code>float</code></td>
|
||||
<td>
|
||||
|
|
@ -770,7 +770,7 @@ unspecified, all request will be delayed.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="HTTPFaultInjection.Delay.fixed_delay" class="oneof oneof-start">
|
||||
<tr id="HTTPFaultInjection-Delay-fixed_delay" class="oneof oneof-start">
|
||||
<td><code>fixedDelay</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#duration">google.protobuf.Duration (oneof)</a></code></td>
|
||||
<td>
|
||||
|
|
@ -778,7 +778,7 @@ unspecified, all request will be delayed.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="HTTPFaultInjection.Delay.exponential_delay" class="oneof">
|
||||
<tr id="HTTPFaultInjection-Delay-exponential_delay" class="oneof">
|
||||
<td><code>exponentialDelay</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#duration">google.protobuf.Duration (oneof)</a></code></td>
|
||||
<td>
|
||||
|
|
@ -788,7 +788,7 @@ values –)</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="HTTPFaultInjection.Delay.override_header_name">
|
||||
<tr id="HTTPFaultInjection-Delay-override_header_name">
|
||||
<td><code>overrideHeaderName</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -832,7 +832,7 @@ spec:
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="HTTPRedirect.uri">
|
||||
<tr id="HTTPRedirect-uri">
|
||||
<td><code>uri</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -842,7 +842,7 @@ request URI being matched as an exact path or prefix.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="HTTPRedirect.authority">
|
||||
<tr id="HTTPRedirect-authority">
|
||||
<td><code>authority</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -884,13 +884,13 @@ spec:
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="HTTPRetry.simple_retry" class="oneof oneof-start">
|
||||
<tr id="HTTPRetry-simple_retry" class="oneof oneof-start">
|
||||
<td><code>simpleRetry</code></td>
|
||||
<td><code><a href="#HTTPRetry.SimpleRetryPolicy">HTTPRetry.SimpleRetryPolicy (oneof)</a></code></td>
|
||||
<td><code><a href="#HTTPRetry-SimpleRetryPolicy">HTTPRetry.SimpleRetryPolicy (oneof)</a></code></td>
|
||||
<td>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="HTTPRetry.custom" class="oneof">
|
||||
<tr id="HTTPRetry-custom" class="oneof">
|
||||
<td><code>custom</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#any">google.protobuf.Any (oneof)</a></code></td>
|
||||
<td>
|
||||
|
|
@ -901,7 +901,7 @@ spec:
|
|||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="HTTPRetry.SimpleRetryPolicy">HTTPRetry.SimpleRetryPolicy</h2>
|
||||
<h2 id="HTTPRetry-SimpleRetryPolicy">HTTPRetry.SimpleRetryPolicy</h2>
|
||||
<section>
|
||||
<table class="message-fields">
|
||||
<thead>
|
||||
|
|
@ -912,7 +912,7 @@ spec:
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="HTTPRetry.SimpleRetryPolicy.attempts">
|
||||
<tr id="HTTPRetry-SimpleRetryPolicy-attempts">
|
||||
<td><code>attempts</code></td>
|
||||
<td><code>int32</code></td>
|
||||
<td>
|
||||
|
|
@ -922,7 +922,7 @@ number of retries attempted depends on the httpReqTimeout.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="HTTPRetry.SimpleRetryPolicy.per_try_timeout">
|
||||
<tr id="HTTPRetry-SimpleRetryPolicy-per_try_timeout">
|
||||
<td><code>perTryTimeout</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#duration">google.protobuf.Duration</a></code></td>
|
||||
<td>
|
||||
|
|
@ -930,7 +930,7 @@ number of retries attempted depends on the httpReqTimeout.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="HTTPRetry.SimpleRetryPolicy.override_header_name">
|
||||
<tr id="HTTPRetry-SimpleRetryPolicy-override_header_name">
|
||||
<td><code>overrideHeaderName</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -977,7 +977,7 @@ spec:
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="HTTPRewrite.uri">
|
||||
<tr id="HTTPRewrite-uri">
|
||||
<td><code>uri</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -987,7 +987,7 @@ provided in this field will replace the corresponding matched prefix.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="HTTPRewrite.authority">
|
||||
<tr id="HTTPRewrite-authority">
|
||||
<td><code>authority</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -1026,13 +1026,13 @@ spec:
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="HTTPTimeout.simple_timeout" class="oneof oneof-start">
|
||||
<tr id="HTTPTimeout-simple_timeout" class="oneof oneof-start">
|
||||
<td><code>simpleTimeout</code></td>
|
||||
<td><code><a href="#HTTPTimeout.SimpleTimeoutPolicy">HTTPTimeout.SimpleTimeoutPolicy (oneof)</a></code></td>
|
||||
<td><code><a href="#HTTPTimeout-SimpleTimeoutPolicy">HTTPTimeout.SimpleTimeoutPolicy (oneof)</a></code></td>
|
||||
<td>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="HTTPTimeout.custom" class="oneof">
|
||||
<tr id="HTTPTimeout-custom" class="oneof">
|
||||
<td><code>custom</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#any">google.protobuf.Any (oneof)</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1043,7 +1043,7 @@ spec:
|
|||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="HTTPTimeout.SimpleTimeoutPolicy">HTTPTimeout.SimpleTimeoutPolicy</h2>
|
||||
<h2 id="HTTPTimeout-SimpleTimeoutPolicy">HTTPTimeout.SimpleTimeoutPolicy</h2>
|
||||
<section>
|
||||
<table class="message-fields">
|
||||
<thead>
|
||||
|
|
@ -1054,7 +1054,7 @@ spec:
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="HTTPTimeout.SimpleTimeoutPolicy.timeout">
|
||||
<tr id="HTTPTimeout-SimpleTimeoutPolicy-timeout">
|
||||
<td><code>timeout</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#duration">google.protobuf.Duration</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1065,7 +1065,7 @@ x-envoy-upstream-rq-timeout-ms HTTP header.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="HTTPTimeout.SimpleTimeoutPolicy.override_header_name">
|
||||
<tr id="HTTPTimeout-SimpleTimeoutPolicy-override_header_name">
|
||||
<td><code>overrideHeaderName</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -1101,7 +1101,7 @@ also effective.</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="IngressRule.port">
|
||||
<tr id="IngressRule-port">
|
||||
<td><code>port</code></td>
|
||||
<td><code>int32</code></td>
|
||||
<td>
|
||||
|
|
@ -1109,7 +1109,7 @@ also effective.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="IngressRule.tls_secret">
|
||||
<tr id="IngressRule-tls_secret">
|
||||
<td><code>tlsSecret</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -1118,7 +1118,7 @@ It is up to the underlying secret store to interpret the path to the secret.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="IngressRule.precedence">
|
||||
<tr id="IngressRule-precedence">
|
||||
<td><code>precedence</code></td>
|
||||
<td><code>int32</code></td>
|
||||
<td>
|
||||
|
|
@ -1129,7 +1129,7 @@ precedence is unspecified.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="IngressRule.match">
|
||||
<tr id="IngressRule-match">
|
||||
<td><code>match</code></td>
|
||||
<td><code><a href="#MatchCondition">MatchCondition</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1138,7 +1138,7 @@ activated.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="IngressRule.destination">
|
||||
<tr id="IngressRule-destination">
|
||||
<td><code>destination</code></td>
|
||||
<td><code><a href="#IstioService">IstioService</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1149,7 +1149,7 @@ of the service and therefore the IstioService’s labels field MUST be empty
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="IngressRule.destination_port" class="oneof oneof-start">
|
||||
<tr id="IngressRule-destination_port" class="oneof oneof-start">
|
||||
<td><code>destinationPort</code></td>
|
||||
<td><code>int32 (oneof)</code></td>
|
||||
<td>
|
||||
|
|
@ -1157,7 +1157,7 @@ of the service and therefore the IstioService’s labels field MUST be empty
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="IngressRule.destination_port_name" class="oneof">
|
||||
<tr id="IngressRule-destination_port_name" class="oneof">
|
||||
<td><code>destinationPortName</code></td>
|
||||
<td><code>string (oneof)</code></td>
|
||||
<td>
|
||||
|
|
@ -1183,7 +1183,7 @@ The FQDN of the service is composed from the name, namespace, and implementation
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="IstioService.name">
|
||||
<tr id="IstioService-name">
|
||||
<td><code>name</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -1191,7 +1191,7 @@ The FQDN of the service is composed from the name, namespace, and implementation
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="IstioService.namespace">
|
||||
<tr id="IstioService-namespace">
|
||||
<td><code>namespace</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -1199,7 +1199,7 @@ The FQDN of the service is composed from the name, namespace, and implementation
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="IstioService.domain">
|
||||
<tr id="IstioService-domain">
|
||||
<td><code>domain</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -1207,7 +1207,7 @@ The FQDN of the service is composed from the name, namespace, and implementation
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="IstioService.service">
|
||||
<tr id="IstioService-service">
|
||||
<td><code>service</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -1215,7 +1215,7 @@ The FQDN of the service is composed from the name, namespace, and implementation
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="IstioService.labels">
|
||||
<tr id="IstioService-labels">
|
||||
<td><code>labels</code></td>
|
||||
<td><code>map<string, string></code></td>
|
||||
<td>
|
||||
|
|
@ -1248,9 +1248,9 @@ component. L4 fault injection is not supported at the moment. –)</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="L4FaultInjection.throttle">
|
||||
<tr id="L4FaultInjection-throttle">
|
||||
<td><code>throttle</code></td>
|
||||
<td><code><a href="#L4FaultInjection.Throttle">L4FaultInjection.Throttle</a></code></td>
|
||||
<td><code><a href="#L4FaultInjection-Throttle">L4FaultInjection.Throttle</a></code></td>
|
||||
<td>
|
||||
<p>Unlike Http services, we have very little context for raw Tcp|Udp
|
||||
connections. We could throttle bandwidth of the connections (slow down
|
||||
|
|
@ -1260,16 +1260,16 @@ We first throttle (if set) and then terminate the connection.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="L4FaultInjection.terminate">
|
||||
<tr id="L4FaultInjection-terminate">
|
||||
<td><code>terminate</code></td>
|
||||
<td><code><a href="#L4FaultInjection.Terminate">L4FaultInjection.Terminate</a></code></td>
|
||||
<td><code><a href="#L4FaultInjection-Terminate">L4FaultInjection.Terminate</a></code></td>
|
||||
<td>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="L4FaultInjection.Terminate">L4FaultInjection.Terminate</h2>
|
||||
<h2 id="L4FaultInjection-Terminate">L4FaultInjection.Terminate</h2>
|
||||
<section>
|
||||
<p>Abruptly reset (terminate) the Tcp connection after it has been
|
||||
established, emulating remote server crash or link failure.</p>
|
||||
|
|
@ -1283,7 +1283,7 @@ established, emulating remote server crash or link failure.</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="L4FaultInjection.Terminate.percent">
|
||||
<tr id="L4FaultInjection-Terminate-percent">
|
||||
<td><code>percent</code></td>
|
||||
<td><code>float</code></td>
|
||||
<td>
|
||||
|
|
@ -1291,7 +1291,7 @@ established, emulating remote server crash or link failure.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="L4FaultInjection.Terminate.terminate_after_period">
|
||||
<tr id="L4FaultInjection-Terminate-terminate_after_period">
|
||||
<td><code>terminateAfterPeriod</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#duration">google.protobuf.Duration</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1303,7 +1303,7 @@ express time interval related configs.</p>
|
|||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="L4FaultInjection.Throttle">L4FaultInjection.Throttle</h2>
|
||||
<h2 id="L4FaultInjection-Throttle">L4FaultInjection.Throttle</h2>
|
||||
<section>
|
||||
<p>Bandwidth throttling for Tcp and Udp connections</p>
|
||||
|
||||
|
|
@ -1316,7 +1316,7 @@ express time interval related configs.</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="L4FaultInjection.Throttle.percent">
|
||||
<tr id="L4FaultInjection-Throttle-percent">
|
||||
<td><code>percent</code></td>
|
||||
<td><code>float</code></td>
|
||||
<td>
|
||||
|
|
@ -1324,7 +1324,7 @@ express time interval related configs.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="L4FaultInjection.Throttle.downstream_limit_bps">
|
||||
<tr id="L4FaultInjection-Throttle-downstream_limit_bps">
|
||||
<td><code>downstreamLimitBps</code></td>
|
||||
<td><code>int64</code></td>
|
||||
<td>
|
||||
|
|
@ -1332,7 +1332,7 @@ express time interval related configs.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="L4FaultInjection.Throttle.upstream_limit_bps">
|
||||
<tr id="L4FaultInjection-Throttle-upstream_limit_bps">
|
||||
<td><code>upstreamLimitBps</code></td>
|
||||
<td><code>int64</code></td>
|
||||
<td>
|
||||
|
|
@ -1340,7 +1340,7 @@ express time interval related configs.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="L4FaultInjection.Throttle.throttle_after_period" class="oneof oneof-start">
|
||||
<tr id="L4FaultInjection-Throttle-throttle_after_period" class="oneof oneof-start">
|
||||
<td><code>throttleAfterPeriod</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#duration">google.protobuf.Duration (oneof)</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1351,7 +1351,7 @@ establish sessions/whatever handshake necessary.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="L4FaultInjection.Throttle.throttle_after_bytes" class="oneof">
|
||||
<tr id="L4FaultInjection-Throttle-throttle_after_bytes" class="oneof">
|
||||
<td><code>throttleAfterBytes</code></td>
|
||||
<td><code>double (oneof)</code></td>
|
||||
<td>
|
||||
|
|
@ -1360,7 +1360,7 @@ transferred to upstream before throttling the bandwidth.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="L4FaultInjection.Throttle.throttle_for_period">
|
||||
<tr id="L4FaultInjection-Throttle-throttle_for_period">
|
||||
<td><code>throttleForPeriod</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#duration">google.protobuf.Duration</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1386,7 +1386,7 @@ support is incomplete. –)</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="L4MatchAttributes.source_subnet">
|
||||
<tr id="L4MatchAttributes-source_subnet">
|
||||
<td><code>sourceSubnet</code></td>
|
||||
<td><code>string[]</code></td>
|
||||
<td>
|
||||
|
|
@ -1395,7 +1395,7 @@ just a.b.c.d</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="L4MatchAttributes.destination_subnet">
|
||||
<tr id="L4MatchAttributes-destination_subnet">
|
||||
<td><code>destinationSubnet</code></td>
|
||||
<td><code>string[]</code></td>
|
||||
<td>
|
||||
|
|
@ -1434,15 +1434,15 @@ spec:
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="LoadBalancing.name" class="oneof oneof-start">
|
||||
<tr id="LoadBalancing-name" class="oneof oneof-start">
|
||||
<td><code>name</code></td>
|
||||
<td><code><a href="#LoadBalancing.SimpleLBPolicy">LoadBalancing.SimpleLBPolicy (oneof)</a></code></td>
|
||||
<td><code><a href="#LoadBalancing-SimpleLBPolicy">LoadBalancing.SimpleLBPolicy (oneof)</a></code></td>
|
||||
<td>
|
||||
<p>Load balancing policy name (as defined in SimpleLBPolicy below)</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="LoadBalancing.custom" class="oneof">
|
||||
<tr id="LoadBalancing-custom" class="oneof">
|
||||
<td><code>custom</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#any">google.protobuf.Any (oneof)</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1453,7 +1453,7 @@ spec:
|
|||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="LoadBalancing.SimpleLBPolicy">LoadBalancing.SimpleLBPolicy</h2>
|
||||
<h2 id="LoadBalancing-SimpleLBPolicy">LoadBalancing.SimpleLBPolicy</h2>
|
||||
<section>
|
||||
<p>Load balancing algorithms supported by Envoy.</p>
|
||||
|
||||
|
|
@ -1465,14 +1465,14 @@ spec:
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="LoadBalancing.SimpleLBPolicy.ROUND_ROBIN">
|
||||
<tr id="LoadBalancing-SimpleLBPolicy-ROUND_ROBIN">
|
||||
<td><code>ROUND_ROBIN</code></td>
|
||||
<td>
|
||||
<p>Simple round robin policy.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="LoadBalancing.SimpleLBPolicy.LEAST_CONN">
|
||||
<tr id="LoadBalancing-SimpleLBPolicy-LEAST_CONN">
|
||||
<td><code>LEAST_CONN</code></td>
|
||||
<td>
|
||||
<p>The least request load balancer uses an O(1) algorithm which selects
|
||||
|
|
@ -1481,7 +1481,7 @@ requests.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="LoadBalancing.SimpleLBPolicy.RANDOM">
|
||||
<tr id="LoadBalancing-SimpleLBPolicy-RANDOM">
|
||||
<td><code>RANDOM</code></td>
|
||||
<td>
|
||||
<p>The random load balancer selects a random healthy host. The random
|
||||
|
|
@ -1535,7 +1535,7 @@ request header must be specified.</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="MatchCondition.source">
|
||||
<tr id="MatchCondition-source">
|
||||
<td><code>source</code></td>
|
||||
<td><code><a href="#IstioService">IstioService</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1543,7 +1543,7 @@ request header must be specified.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="MatchCondition.tcp">
|
||||
<tr id="MatchCondition-tcp">
|
||||
<td><code>tcp</code></td>
|
||||
<td><code><a href="#L4MatchAttributes">L4MatchAttributes</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1551,7 +1551,7 @@ request header must be specified.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="MatchCondition.udp">
|
||||
<tr id="MatchCondition-udp">
|
||||
<td><code>udp</code></td>
|
||||
<td><code><a href="#L4MatchAttributes">L4MatchAttributes</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1559,7 +1559,7 @@ request header must be specified.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="MatchCondition.request">
|
||||
<tr id="MatchCondition-request">
|
||||
<td><code>request</code></td>
|
||||
<td><code><a href="#MatchRequest">MatchRequest</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1583,7 +1583,7 @@ request header must be specified.</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="MatchRequest.headers">
|
||||
<tr id="MatchRequest-headers">
|
||||
<td><code>headers</code></td>
|
||||
<td><code>map<string, <a href="#StringMatch">StringMatch</a>></code></td>
|
||||
<td>
|
||||
|
|
@ -1649,7 +1649,7 @@ spec:
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="RouteRule.destination">
|
||||
<tr id="RouteRule-destination">
|
||||
<td><code>destination</code></td>
|
||||
<td><code><a href="#IstioService">IstioService</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1663,7 +1663,7 @@ of the service and therefore the IstioService’s labels field MUST be empty
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="RouteRule.precedence">
|
||||
<tr id="RouteRule-precedence">
|
||||
<td><code>precedence</code></td>
|
||||
<td><code>int32</code></td>
|
||||
<td>
|
||||
|
|
@ -1675,7 +1675,7 @@ unspecified.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="RouteRule.match">
|
||||
<tr id="RouteRule-match">
|
||||
<td><code>match</code></td>
|
||||
<td><code><a href="#MatchCondition">MatchCondition</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1685,7 +1685,7 @@ traffic.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="RouteRule.route">
|
||||
<tr id="RouteRule-route">
|
||||
<td><code>route</code></td>
|
||||
<td><code><a href="#DestinationWeight">DestinationWeight[]</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1697,7 +1697,7 @@ traffic it receives.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="RouteRule.redirect">
|
||||
<tr id="RouteRule-redirect">
|
||||
<td><code>redirect</code></td>
|
||||
<td><code><a href="#HTTPRedirect">HTTPRedirect</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1707,7 +1707,7 @@ redirect to a different URI or Authority.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="RouteRule.rewrite">
|
||||
<tr id="RouteRule-rewrite">
|
||||
<td><code>rewrite</code></td>
|
||||
<td><code><a href="#HTTPRewrite">HTTPRewrite</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1716,7 +1716,7 @@ Redirect primitive. Rewrite will be performed before forwarding.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="RouteRule.websocket_upgrade">
|
||||
<tr id="RouteRule-websocket_upgrade">
|
||||
<td><code>websocketUpgrade</code></td>
|
||||
<td><code>bool</code></td>
|
||||
<td>
|
||||
|
|
@ -1728,7 +1728,7 @@ will be rejected.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="RouteRule.http_req_timeout">
|
||||
<tr id="RouteRule-http_req_timeout">
|
||||
<td><code>httpReqTimeout</code></td>
|
||||
<td><code><a href="#HTTPTimeout">HTTPTimeout</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1736,7 +1736,7 @@ will be rejected.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="RouteRule.http_req_retries">
|
||||
<tr id="RouteRule-http_req_retries">
|
||||
<td><code>httpReqRetries</code></td>
|
||||
<td><code><a href="#HTTPRetry">HTTPRetry</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1744,7 +1744,7 @@ will be rejected.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="RouteRule.http_fault">
|
||||
<tr id="RouteRule-http_fault">
|
||||
<td><code>httpFault</code></td>
|
||||
<td><code><a href="#HTTPFaultInjection">HTTPFaultInjection</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1752,7 +1752,7 @@ will be rejected.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="RouteRule.l4_fault">
|
||||
<tr id="RouteRule-l4_fault">
|
||||
<td><code>l4Fault</code></td>
|
||||
<td><code><a href="#L4FaultInjection">L4FaultInjection</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1760,7 +1760,7 @@ will be rejected.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="RouteRule.mirror">
|
||||
<tr id="RouteRule-mirror">
|
||||
<td><code>mirror</code></td>
|
||||
<td><code><a href="#IstioService">IstioService</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1772,7 +1772,7 @@ Statistics will be generated for the mirrored destination.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="RouteRule.cors_policy">
|
||||
<tr id="RouteRule-cors_policy">
|
||||
<td><code>corsPolicy</code></td>
|
||||
<td><code><a href="#CorsPolicy">CorsPolicy</a></code></td>
|
||||
<td>
|
||||
|
|
@ -1782,7 +1782,7 @@ further details about cross origin resource sharing.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="RouteRule.append_headers">
|
||||
<tr id="RouteRule-append_headers">
|
||||
<td><code>appendHeaders</code></td>
|
||||
<td><code>map<string, string></code></td>
|
||||
<td>
|
||||
|
|
@ -1807,7 +1807,7 @@ destnation service.</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="StringMatch.exact" class="oneof oneof-start">
|
||||
<tr id="StringMatch-exact" class="oneof oneof-start">
|
||||
<td><code>exact</code></td>
|
||||
<td><code>string (oneof)</code></td>
|
||||
<td>
|
||||
|
|
@ -1815,7 +1815,7 @@ destnation service.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="StringMatch.prefix" class="oneof">
|
||||
<tr id="StringMatch-prefix" class="oneof">
|
||||
<td><code>prefix</code></td>
|
||||
<td><code>string (oneof)</code></td>
|
||||
<td>
|
||||
|
|
@ -1823,7 +1823,7 @@ destnation service.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="StringMatch.regex" class="oneof">
|
||||
<tr id="StringMatch-regex" class="oneof">
|
||||
<td><code>regex</code></td>
|
||||
<td><code>string (oneof)</code></td>
|
||||
<td>
|
||||
|
|
|
|||
|
|
@ -63,60 +63,6 @@ This controls how frequently the complete resync occurs.</p>
|
|||
|
||||
<p>Default: 5 minutes</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Params.cluster_domain_name">
|
||||
<td><code>clusterDomainName</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
<p>Configures the cluster domain name to use for service name normalization.</p>
|
||||
|
||||
<p>Default: svc.cluster.local</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Params.pod_label_for_service">
|
||||
<td><code>podLabelForService</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
<p>In order to extract the service associated with a source, destination, or
|
||||
origin, this adapter relies on pod labels. In particular, it looks for
|
||||
the value of a specific label, as specified by this parameter.</p>
|
||||
|
||||
<p>Default: app</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Params.pod_label_for_istio_component_service">
|
||||
<td><code>podLabelForIstioComponentService</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
<p>In order to extract the service associated with a source, destination, or
|
||||
origin, this adapter relies on pod labels. In particular, it looks for
|
||||
the value of a specific label for istio component services, as specified
|
||||
by this parameter.</p>
|
||||
|
||||
<p>Default: istio</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Params.lookup_ingress_source_and_origin_values">
|
||||
<td><code>lookupIngressSourceAndOriginValues</code></td>
|
||||
<td><code>bool</code></td>
|
||||
<td>
|
||||
<p>Default: false</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Params.fully_qualified_istio_ingress_service_name">
|
||||
<td><code>fullyQualifiedIstioIngressServiceName</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
<p>Istio ingress service string. This is used to identify the
|
||||
ingress service in requests.</p>
|
||||
|
||||
<p>Default: “ingress.istio-system.svc.cluster.local”</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
|
|
|||
|
|
@ -1,18 +1,18 @@
|
|||
---
|
||||
title: Stackdriver
|
||||
description: Adapter to deliver logs and metrics to Stackdriver
|
||||
description: Adapter to deliver logs, metrics, and traces to Stackdriver
|
||||
location: https://istio.io/docs/reference/config/policy-and-telemetry/adapters/stackdriver.html
|
||||
layout: protoc-gen-docs
|
||||
generator: protoc-gen-docs
|
||||
aliases:
|
||||
- /docs/reference/config/adapters/stackdriver.html
|
||||
number_of_entries: 11
|
||||
number_of_entries: 12
|
||||
---
|
||||
<p>The <code>stackdriver</code> adapter enables Istio to deliver log and metric data to the
|
||||
<a href="https://cloud.google.com/stackdriver/">Stackdriver</a> logging and monitoring backend.</p>
|
||||
<p>The <code>stackdriver</code> adapter enables Istio to deliver log, metric and traces to the
|
||||
<a href="https://cloud.google.com/stackdriver/">Stackdriver</a> backend.</p>
|
||||
|
||||
<p>This adapter supports the <a href="/docs/reference/config/policy-and-telemetry/templates/metric/">metric template</a>,
|
||||
and the <a href="/docs/reference/config/policy-and-telemetry/templates/logentry/">logentry template</a>.</p>
|
||||
<p>This adapter supports the <a href="/docs/reference/config/policy-and-telemetry/templates/metric/">metric template</a> and
|
||||
the <a href="/docs/reference/config/policy-and-telemetry/templates/logentry/">logentry template</a>.
|
||||
|
||||
<h2 id="Params">Params</h2>
|
||||
<section>
|
||||
|
|
@ -96,6 +96,14 @@ or <code>./testdata/my-test-account-creds.json</code>.</p>
|
|||
<td>
|
||||
<p>A map of Istio LogEntry name to Stackdriver log info.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Params.trace">
|
||||
<td><code>trace</code></td>
|
||||
<td><code><a href="#Params.Trace">Params.Trace</a></code></td>
|
||||
<td>
|
||||
<p>Stackdriver Trace configuration.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
|
@ -524,6 +532,30 @@ buckets are the underflow and overflow buckets.</p>
|
|||
<td>
|
||||
<p>Lower bound of the first bucket.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="Params.Trace">Params.Trace</h2>
|
||||
<section>
|
||||
<p>Details of Stackdriver Trace configuration for tracespan template.</p>
|
||||
|
||||
<table class="message-fields">
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Type</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="Params.Trace.sample_probability">
|
||||
<td><code>sampleProbability</code></td>
|
||||
<td><code>double</code></td>
|
||||
<td>
|
||||
<p>Proability that a particular trace ID will be sampled.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
|
|
|||
|
|
@ -29,21 +29,21 @@ constructed using the instance ‘RequestCountByService’.</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="Action.handler">
|
||||
<tr id="Action-handler">
|
||||
<td><code>handler</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
<p>Required. Fully qualified name of the handler to invoke.
|
||||
Must match the <code>name</code> of a <a href="#Handler.name">Handler</a>.</p>
|
||||
Must match the <code>name</code> of a <a href="#Handler-name">Handler</a>.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Action.instances">
|
||||
<tr id="Action-instances">
|
||||
<td><code>instances</code></td>
|
||||
<td><code>string[]</code></td>
|
||||
<td>
|
||||
<p>Required. Each value must match the fully qualified name of the
|
||||
<a href="#Instance.name">Instance</a>s.
|
||||
<a href="#Instance-name">Instance</a>s.
|
||||
Referenced instances are evaluated by resolving the attributes/literals for all the fields.
|
||||
The constructed objects are then passed to the <code>handler</code> referenced within this action.</p>
|
||||
|
||||
|
|
@ -66,7 +66,7 @@ of an Istio deployment.</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="AttributeManifest.revision">
|
||||
<tr id="AttributeManifest-revision">
|
||||
<td><code>revision</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -74,7 +74,7 @@ of an Istio deployment.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="AttributeManifest.name">
|
||||
<tr id="AttributeManifest-name">
|
||||
<td><code>name</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -84,9 +84,9 @@ the proxy (with the canonical name “istio-proxy”) or the name of an
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="AttributeManifest.attributes">
|
||||
<tr id="AttributeManifest-attributes">
|
||||
<td><code>attributes</code></td>
|
||||
<td><code>map<string, <a href="#AttributeManifest.AttributeInfo">AttributeManifest.AttributeInfo</a>></code></td>
|
||||
<td><code>map<string, <a href="#AttributeManifest-AttributeInfo">AttributeManifest.AttributeInfo</a>></code></td>
|
||||
<td>
|
||||
<p>The set of attributes this Istio component will be responsible for producing at runtime.
|
||||
We map from attribute name to the attribute’s specification. The name of an attribute,
|
||||
|
|
@ -108,11 +108,11 @@ request.count-my.component.</p>
|
|||
</tbody>
|
||||
</table>
|
||||
</section>
|
||||
<h2 id="AttributeManifest.AttributeInfo">AttributeManifest.AttributeInfo</h2>
|
||||
<h2 id="AttributeManifest-AttributeInfo">AttributeManifest.AttributeInfo</h2>
|
||||
<section>
|
||||
<p>AttributeInfo describes the schema of an Istio <code>Attribute</code>.</p>
|
||||
|
||||
<h4 id="istio-attributes">Istio Attributes</h4>
|
||||
<h3 id="istio-attributes">Istio Attributes</h3>
|
||||
|
||||
<p>Istio uses <code>attributes</code> to describe runtime activities of Istio services.
|
||||
An Istio attribute carries a specific piece of information about an activity,
|
||||
|
|
@ -130,7 +130,7 @@ functionality by collecting, generating, and operating on attributes.
|
|||
For example, the proxy collects the error code attribute, and the logging
|
||||
stores it into a log.</p>
|
||||
|
||||
<h4 id="design">Design</h4>
|
||||
<h3 id="design">Design</h3>
|
||||
|
||||
<p>Each Istio attribute must conform to an <code>AttributeInfo</code> in an
|
||||
<code>AttributeManifest</code> in the current Istio deployment at runtime. An
|
||||
|
|
@ -144,7 +144,7 @@ specification, because passing attribute using JSON, XML, or Protocol Buffers
|
|||
does not change the semantics of the attribute. Different implementations
|
||||
can choose different representations based on their needs.</p>
|
||||
|
||||
<h4 id="http-mapping">HTTP Mapping</h4>
|
||||
<h3 id="http-mapping">HTTP Mapping</h3>
|
||||
|
||||
<p>Because many systems already have REST APIs, it makes sense to define a
|
||||
standard HTTP mapping for Istio attributes that are compatible with typical
|
||||
|
|
@ -161,7 +161,7 @@ encoding scheme will be decided later.</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="AttributeManifest.AttributeInfo.description">
|
||||
<tr id="AttributeManifest-AttributeInfo-description">
|
||||
<td><code>description</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -169,7 +169,7 @@ encoding scheme will be decided later.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="AttributeManifest.AttributeInfo.value_type">
|
||||
<tr id="AttributeManifest-AttributeInfo-value_type">
|
||||
<td><code>valueType</code></td>
|
||||
<td><code><a href="#ValueType">ValueType</a></code></td>
|
||||
<td>
|
||||
|
|
@ -194,7 +194,7 @@ Connection is part of the handler custom resource and is specified alongside ada
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="Connection.address">
|
||||
<tr id="Connection-address">
|
||||
<td><code>address</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -208,7 +208,7 @@ Connection is part of the handler custom resource and is specified alongside ada
|
|||
<h2 id="DNSName">DNSName</h2>
|
||||
<section>
|
||||
<p>An instance field of type DNSName denotes that the expression for the field must evalaute to
|
||||
<a href="#ValueType.DNS_NAME">ValueType.DNS_NAME</a></p>
|
||||
<a href="#ValueType-DNS_NAME">ValueType.DNS_NAME</a></p>
|
||||
|
||||
<p>Objects of type DNSName are also passed to the adapters during request-time for the instance fields of
|
||||
type DNSName</p>
|
||||
|
|
@ -222,7 +222,7 @@ type DNSName</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="DNSName.value">
|
||||
<tr id="DNSName-value">
|
||||
<td><code>value</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -236,7 +236,7 @@ type DNSName</p>
|
|||
<h2 id="Duration">Duration</h2>
|
||||
<section>
|
||||
<p>An instance field of type Duration denotes that the expression for the field must evalaute to
|
||||
<a href="#ValueType.DURATION">ValueType.DURATION</a></p>
|
||||
<a href="#ValueType-DURATION">ValueType.DURATION</a></p>
|
||||
|
||||
<p>Objects of type Duration are also passed to the adapters during request-time for the instance fields of
|
||||
type Duration</p>
|
||||
|
|
@ -250,7 +250,7 @@ type Duration</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="Duration.value">
|
||||
<tr id="Duration-value">
|
||||
<td><code>value</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#duration">google.protobuf.Duration</a></code></td>
|
||||
<td>
|
||||
|
|
@ -265,7 +265,7 @@ type Duration</p>
|
|||
<section>
|
||||
<p>DO NOT USE !! Under Development
|
||||
An instance field of type EmailAddress denotes that the expression for the field must evalaute to
|
||||
<a href="#ValueType.EMAIL_ADDRESS">ValueType.EMAIL_ADDRESS</a></p>
|
||||
<a href="#ValueType-EMAIL_ADDRESS">ValueType.EMAIL_ADDRESS</a></p>
|
||||
|
||||
<p>Objects of type EmailAddress are also passed to the adapters during request-time for the instance fields of
|
||||
type EmailAddress</p>
|
||||
|
|
@ -279,7 +279,7 @@ type EmailAddress</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="EmailAddress.value">
|
||||
<tr id="EmailAddress-value">
|
||||
<td><code>value</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -352,25 +352,39 @@ spec:
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="Handler.name">
|
||||
<tr id="Handler-name">
|
||||
<td><code>name</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
<p>Required. Must be unique in the entire mixer configuration. Used by <a href="#Action.handler">Actions</a>
|
||||
<p>Required. Must be unique in the entire mixer configuration. Used by <a href="#Action-handler">Actions</a>
|
||||
to refer to this handler.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Handler.adapter">
|
||||
<td><code>adapter</code></td>
|
||||
<tr id="Handler-compiled_adapter">
|
||||
<td><code>compiledAdapter</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
<p>Required. The name of a specific adapter implementation. An adapter’s
|
||||
implementation name is typically a constant in its code.</p>
|
||||
<p>Required. The name of the compiled in adapter this handler instantiates. For referencing non compiled-in
|
||||
adapters, use the <code>adapter</code> field instead.</p>
|
||||
|
||||
<p>The value must match the name of the available adapter Mixer is built with. An adapter’s name is typically a
|
||||
constant in its code.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Handler.params">
|
||||
<tr id="Handler-adapter">
|
||||
<td><code>adapter</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
<p>Required. The name of a specific adapter implementation. For referencing compiled-in
|
||||
adapters, use the <code>compiled_adapter</code> field instead.</p>
|
||||
|
||||
<p>An adapter’s implementation name is typically a constant in its code.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Handler-params">
|
||||
<td><code>params</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#struct">google.protobuf.Struct</a></code></td>
|
||||
<td>
|
||||
|
|
@ -379,7 +393,7 @@ proto defined by the adapter implementation; this varies depending on the value
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Handler.connection">
|
||||
<tr id="Handler-connection">
|
||||
<td><code>connection</code></td>
|
||||
<td><code><a href="#Connection">Connection</a></code></td>
|
||||
<td>
|
||||
|
|
@ -394,7 +408,7 @@ This is used if the adapter is not compiled into Mixer binary and is running as
|
|||
<h2 id="IPAddress">IPAddress</h2>
|
||||
<section>
|
||||
<p>An instance field of type IPAddress denotes that the expression for the field must evalaute to
|
||||
<a href="#ValueType.IP_ADDRESS">ValueType.IP_ADDRESS</a></p>
|
||||
<a href="#ValueType-IP_ADDRESS">ValueType.IP_ADDRESS</a></p>
|
||||
|
||||
<p>Objects of type IPAddress are also passed to the adapters during request-time for the instance fields of
|
||||
type IPAddress</p>
|
||||
|
|
@ -408,7 +422,7 @@ type IPAddress</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="IPAddress.value">
|
||||
<tr id="IPAddress-value">
|
||||
<td><code>value</code></td>
|
||||
<td><code>bytes</code></td>
|
||||
<td>
|
||||
|
|
@ -450,7 +464,7 @@ Instances produced with this instance can be referenced by <a href="#Action">Act
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="Instance.name">
|
||||
<tr id="Instance-name">
|
||||
<td><code>name</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -461,16 +475,29 @@ to an instance produced by this instance.</p>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Instance.template">
|
||||
<td><code>template</code></td>
|
||||
<tr id="Instance-compiled_template">
|
||||
<td><code>compiledTemplate</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
<p>Required. The name of the template this instance creates instances for.
|
||||
The value must match the name of the available template in scope.</p>
|
||||
<p>Required. The name of the compiled in template this instance creates instances for. For referencing non compiled-in
|
||||
templates, use the <code>template</code> field instead.</p>
|
||||
|
||||
<p>The value must match the name of the available template Mixer is built with.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Instance.params">
|
||||
<tr id="Instance-template">
|
||||
<td><code>template</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
<p>Required. The name of the template this instance creates instances for. For referencing compiled-in
|
||||
templates, use the <code>compiled_template</code> field instead.</p>
|
||||
|
||||
<p>The value must match the name of the available template in scope.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Instance-params">
|
||||
<td><code>params</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#struct">google.protobuf.Struct</a></code></td>
|
||||
<td>
|
||||
|
|
@ -506,7 +533,7 @@ instance constructed using the ‘RequestCountByService’ instance.</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="Rule.match">
|
||||
<tr id="Rule-match">
|
||||
<td><code>match</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -526,7 +553,7 @@ name starts with “ratings”</li>
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Rule.actions">
|
||||
<tr id="Rule-actions">
|
||||
<td><code>actions</code></td>
|
||||
<td><code><a href="#Action">Action[]</a></code></td>
|
||||
<td>
|
||||
|
|
@ -540,7 +567,7 @@ name starts with “ratings”</li>
|
|||
<h2 id="TimeStamp">TimeStamp</h2>
|
||||
<section>
|
||||
<p>An instance field of type TimeStamp denotes that the expression for the field must evalaute to
|
||||
<a href="#ValueType.TIMESTAMP">ValueType.TIMESTAMP</a></p>
|
||||
<a href="#ValueType-TIMESTAMP">ValueType.TIMESTAMP</a></p>
|
||||
|
||||
<p>Objects of type TimeStamp are also passed to the adapters during request-time for the instance fields of
|
||||
type TimeStamp</p>
|
||||
|
|
@ -554,7 +581,7 @@ type TimeStamp</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="TimeStamp.value">
|
||||
<tr id="TimeStamp-value">
|
||||
<td><code>value</code></td>
|
||||
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#timestamp">google.protobuf.Timestamp</a></code></td>
|
||||
<td>
|
||||
|
|
@ -569,7 +596,7 @@ type TimeStamp</p>
|
|||
<section>
|
||||
<p>DO NOT USE !! Under Development
|
||||
An instance field of type Uri denotes that the expression for the field must evalaute to
|
||||
<a href="#ValueType.URI">ValueType.URI</a></p>
|
||||
<a href="#ValueType-URI">ValueType.URI</a></p>
|
||||
|
||||
<p>Objects of type Uri are also passed to the adapters during request-time for the instance fields of
|
||||
type Uri</p>
|
||||
|
|
@ -583,7 +610,7 @@ type Uri</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="Uri.value">
|
||||
<tr id="Uri-value">
|
||||
<td><code>value</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
|
|
@ -615,7 +642,7 @@ the equivalent oneof field in <code>Value</code> is populated by Mixer and passe
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="Value.string_value" class="oneof oneof-start">
|
||||
<tr id="Value-string_value" class="oneof oneof-start">
|
||||
<td><code>stringValue</code></td>
|
||||
<td><code>string (oneof)</code></td>
|
||||
<td>
|
||||
|
|
@ -623,7 +650,7 @@ the equivalent oneof field in <code>Value</code> is populated by Mixer and passe
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Value.int64_value" class="oneof">
|
||||
<tr id="Value-int64_value" class="oneof">
|
||||
<td><code>int64Value</code></td>
|
||||
<td><code>int64 (oneof)</code></td>
|
||||
<td>
|
||||
|
|
@ -631,7 +658,7 @@ the equivalent oneof field in <code>Value</code> is populated by Mixer and passe
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Value.double_value" class="oneof">
|
||||
<tr id="Value-double_value" class="oneof">
|
||||
<td><code>doubleValue</code></td>
|
||||
<td><code>double (oneof)</code></td>
|
||||
<td>
|
||||
|
|
@ -639,7 +666,7 @@ the equivalent oneof field in <code>Value</code> is populated by Mixer and passe
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Value.bool_value" class="oneof">
|
||||
<tr id="Value-bool_value" class="oneof">
|
||||
<td><code>boolValue</code></td>
|
||||
<td><code>bool (oneof)</code></td>
|
||||
<td>
|
||||
|
|
@ -647,7 +674,7 @@ the equivalent oneof field in <code>Value</code> is populated by Mixer and passe
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Value.ip_address_value" class="oneof">
|
||||
<tr id="Value-ip_address_value" class="oneof">
|
||||
<td><code>ipAddressValue</code></td>
|
||||
<td><code><a href="#IPAddress">IPAddress (oneof)</a></code></td>
|
||||
<td>
|
||||
|
|
@ -655,7 +682,7 @@ the equivalent oneof field in <code>Value</code> is populated by Mixer and passe
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Value.timestamp_value" class="oneof">
|
||||
<tr id="Value-timestamp_value" class="oneof">
|
||||
<td><code>timestampValue</code></td>
|
||||
<td><code><a href="#TimeStamp">TimeStamp (oneof)</a></code></td>
|
||||
<td>
|
||||
|
|
@ -663,7 +690,7 @@ the equivalent oneof field in <code>Value</code> is populated by Mixer and passe
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Value.duration_value" class="oneof">
|
||||
<tr id="Value-duration_value" class="oneof">
|
||||
<td><code>durationValue</code></td>
|
||||
<td><code><a href="#Duration">Duration (oneof)</a></code></td>
|
||||
<td>
|
||||
|
|
@ -671,7 +698,7 @@ the equivalent oneof field in <code>Value</code> is populated by Mixer and passe
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Value.email_address_value" class="oneof">
|
||||
<tr id="Value-email_address_value" class="oneof">
|
||||
<td><code>emailAddressValue</code></td>
|
||||
<td><code><a href="#EmailAddress">EmailAddress (oneof)</a></code></td>
|
||||
<td>
|
||||
|
|
@ -679,7 +706,7 @@ the equivalent oneof field in <code>Value</code> is populated by Mixer and passe
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Value.dns_name_value" class="oneof">
|
||||
<tr id="Value-dns_name_value" class="oneof">
|
||||
<td><code>dnsNameValue</code></td>
|
||||
<td><code><a href="#DNSName">DNSName (oneof)</a></code></td>
|
||||
<td>
|
||||
|
|
@ -687,7 +714,7 @@ the equivalent oneof field in <code>Value</code> is populated by Mixer and passe
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Value.uri_value" class="oneof">
|
||||
<tr id="Value-uri_value" class="oneof">
|
||||
<td><code>uriValue</code></td>
|
||||
<td><code><a href="#Uri">Uri (oneof)</a></code></td>
|
||||
<td>
|
||||
|
|
@ -713,84 +740,84 @@ fields of other descriptors.</p>
|
|||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr id="ValueType.VALUE_TYPE_UNSPECIFIED">
|
||||
<tr id="ValueType-VALUE_TYPE_UNSPECIFIED">
|
||||
<td><code>VALUE_TYPE_UNSPECIFIED</code></td>
|
||||
<td>
|
||||
<p>Invalid, default value.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="ValueType.STRING">
|
||||
<tr id="ValueType-STRING">
|
||||
<td><code>STRING</code></td>
|
||||
<td>
|
||||
<p>An undiscriminated variable-length string.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="ValueType.INT64">
|
||||
<tr id="ValueType-INT64">
|
||||
<td><code>INT64</code></td>
|
||||
<td>
|
||||
<p>An undiscriminated 64-bit signed integer.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="ValueType.DOUBLE">
|
||||
<tr id="ValueType-DOUBLE">
|
||||
<td><code>DOUBLE</code></td>
|
||||
<td>
|
||||
<p>An undiscriminated 64-bit floating-point value.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="ValueType.BOOL">
|
||||
<tr id="ValueType-BOOL">
|
||||
<td><code>BOOL</code></td>
|
||||
<td>
|
||||
<p>An undiscriminated boolean value.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="ValueType.TIMESTAMP">
|
||||
<tr id="ValueType-TIMESTAMP">
|
||||
<td><code>TIMESTAMP</code></td>
|
||||
<td>
|
||||
<p>A point in time.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="ValueType.IP_ADDRESS">
|
||||
<tr id="ValueType-IP_ADDRESS">
|
||||
<td><code>IP_ADDRESS</code></td>
|
||||
<td>
|
||||
<p>An IP address.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="ValueType.EMAIL_ADDRESS">
|
||||
<tr id="ValueType-EMAIL_ADDRESS">
|
||||
<td><code>EMAIL_ADDRESS</code></td>
|
||||
<td>
|
||||
<p>An email address.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="ValueType.URI">
|
||||
<tr id="ValueType-URI">
|
||||
<td><code>URI</code></td>
|
||||
<td>
|
||||
<p>A URI.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="ValueType.DNS_NAME">
|
||||
<tr id="ValueType-DNS_NAME">
|
||||
<td><code>DNS_NAME</code></td>
|
||||
<td>
|
||||
<p>A DNS name.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="ValueType.DURATION">
|
||||
<tr id="ValueType-DURATION">
|
||||
<td><code>DURATION</code></td>
|
||||
<td>
|
||||
<p>A span between two points in time.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="ValueType.STRING_MAP">
|
||||
<tr id="ValueType-STRING_MAP">
|
||||
<td><code>STRING_MAP</code></td>
|
||||
<td>
|
||||
<p>A map string -> string, typically used by headers.</p>
|
||||
|
|
|
|||
|
|
@ -81,14 +81,6 @@ to assign values to the generated attributes using the <code>$out.<field name
|
|||
<td>
|
||||
<p>Refers to source pod namespace. attribute<em>bindings can refer to this field using $out.source</em>namespace</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="OutputTemplate.source_service">
|
||||
<td><code>sourceService</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
<p>Refers to source service. attribute<em>bindings can refer to this field using $out.source</em>service</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="OutputTemplate.source_service_account_name">
|
||||
|
|
@ -105,6 +97,38 @@ to assign values to the generated attributes using the <code>$out.<field name
|
|||
<td>
|
||||
<p>Refers to source pod host ip address. attribute<em>bindings can refer to this field using $out.source</em>host_ip</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="OutputTemplate.source_workload_uid">
|
||||
<td><code>sourceWorkloadUid</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
<p>Refers to the Istio workload identifier for the source pod. Attribute<em>bindings can refer to this field using $out.source</em>workload_uid</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="OutputTemplate.source_workload_name">
|
||||
<td><code>sourceWorkloadName</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
<p>Refers to the Istio workload name for the source pod. Attribute<em>bindings can refer to this field using $out.source</em>workload_name</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="OutputTemplate.source_workload_namespace">
|
||||
<td><code>sourceWorkloadNamespace</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
<p>Refers to the Istio workload namespace for the source pod. Attribute<em>bindings can refer to this field using $out.source</em>workload_namespace</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="OutputTemplate.source_owner">
|
||||
<td><code>sourceOwner</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
<p>Refers to the (controlling) owner of the source pod. Attribute<em>bindings can refer to this field using $out.source</em>owner</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="OutputTemplate.destination_pod_ip">
|
||||
|
|
@ -137,14 +161,6 @@ to assign values to the generated attributes using the <code>$out.<field name
|
|||
<td>
|
||||
<p>Refers to destination pod namespace. attribute<em>bindings can refer to this field using $out.destination</em>namespace</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="OutputTemplate.destination_service">
|
||||
<td><code>destinationService</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
<p>Refers to destination service. attribute<em>bindings can refer to this field using $out.destination</em>service</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="OutputTemplate.destination_service_account_name">
|
||||
|
|
@ -163,59 +179,35 @@ to assign values to the generated attributes using the <code>$out.<field name
|
|||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="OutputTemplate.origin_pod_ip">
|
||||
<td><code>originPodIp</code></td>
|
||||
<td><code><a href="#istio.policy.v1beta1.IPAddress">istio.policy.v1beta1.IPAddress</a></code></td>
|
||||
<td>
|
||||
<p>Refers to origin pod ip address. attribute<em>bindings can refer to this field using $out.origin</em>pod_ip</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="OutputTemplate.origin_pod_name">
|
||||
<td><code>originPodName</code></td>
|
||||
<tr id="OutputTemplate.destination_owner">
|
||||
<td><code>destinationOwner</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
<p>Refers to origin pod name. attribute<em>bindings can refer to this field using $out.origin</em>pod_name</p>
|
||||
<p>Refers to the (controlling) owner of the destination pod. Attribute<em>bindings can refer to this field using $out.destination</em>owner</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="OutputTemplate.origin_labels">
|
||||
<td><code>originLabels</code></td>
|
||||
<td><code>map<string, string></code></td>
|
||||
<td>
|
||||
<p>Refers to origin pod labels. attribute<em>bindings can refer to this field using $out.origin</em>labels</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="OutputTemplate.origin_namespace">
|
||||
<td><code>originNamespace</code></td>
|
||||
<tr id="OutputTemplate.destination_workload_uid">
|
||||
<td><code>destinationWorkloadUid</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
<p>Refers to origin pod namespace. attribute<em>bindings can refer to this field using $out.origin</em>namespace</p>
|
||||
<p>Refers to the Istio workload identifier for the destination pod. Attribute<em>bindings can refer to this field using $out.destination</em>workload_uid</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="OutputTemplate.origin_service">
|
||||
<td><code>originService</code></td>
|
||||
<tr id="OutputTemplate.destination_workload_name">
|
||||
<td><code>destinationWorkloadName</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
<p>Refers to origin service. attribute<em>bindings can refer to this field using $out.origin</em>service</p>
|
||||
<p>Refers to the Istio workload name for the destination pod. Attribute<em>bindings can refer to this field using $out.destination</em>workload_name</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="OutputTemplate.origin_service_account_name">
|
||||
<td><code>originServiceAccountName</code></td>
|
||||
<tr id="OutputTemplate.destination_workload_namespace">
|
||||
<td><code>destinationWorkloadNamespace</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
<p>Refers to origin pod service account name. attribute<em>bindings can refer to this field using $out.origin</em>service<em>account</em>name</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="OutputTemplate.origin_host_ip">
|
||||
<td><code>originHostIp</code></td>
|
||||
<td><code><a href="#istio.policy.v1beta1.IPAddress">istio.policy.v1beta1.IPAddress</a></code></td>
|
||||
<td>
|
||||
<p>Refers to origin pod host ip address. attribute<em>bindings can refer to this field using $out.origin</em>host_ip</p>
|
||||
<p>Refers to the Istio workload name for the destination pod. Attribute<em>bindings can refer to this field using $out.destination</em>workload_namespace</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
|
|
@ -268,22 +260,6 @@ generates values related to pod information.</p>
|
|||
<td>
|
||||
<p>Destination pod’s ip.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Template.origin_uid">
|
||||
<td><code>originUid</code></td>
|
||||
<td><code>string</code></td>
|
||||
<td>
|
||||
<p>Origin pod’s uid. Must be of the form: “kubernetes://pod.namespace”</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="Template.origin_ip">
|
||||
<td><code>originIp</code></td>
|
||||
<td><code><a href="#istio.policy.v1beta1.IPAddress">istio.policy.v1beta1.IPAddress</a></code></td>
|
||||
<td>
|
||||
<p>Origin pod’s ip.</p>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
|
|
|||
|
|
@ -341,7 +341,7 @@ $ kubectl create -n <namespace> -f <your-app-spec>.yaml
|
|||
```
|
||||
|
||||
If you do not have the Istio-sidecar-injector installed, you must
|
||||
use [istioctl kube-inject](/docs/reference/commands/istioctl/#istioctl kube-inject) to
|
||||
use [istioctl kube-inject](/docs/reference/commands/istioctl/#istioctl-kube-inject) to
|
||||
manually inject Envoy containers in your application pods before deploying them:
|
||||
|
||||
```command
|
||||
|
|
|
|||
|
|
@ -282,6 +282,6 @@ cloud provider specific knowledge and configuration.
|
|||
* Learn more about [service entries](/docs/concepts/traffic-management/rules-configuration/#service-entries).
|
||||
|
||||
* Learn how to setup
|
||||
[timeouts](/docs/reference/config/istio.networking.v1alpha3/#HTTPRoute.timeout),
|
||||
[retries](/docs/reference/config/istio.networking.v1alpha3/#HTTPRoute.retries),
|
||||
[timeouts](/docs/reference/config/istio.networking.v1alpha3/#HTTPRoute-timeout),
|
||||
[retries](/docs/reference/config/istio.networking.v1alpha3/#HTTPRoute-retries),
|
||||
and [circuit breakers](/docs/reference/config/istio.networking.v1alpha3/#OutlierDetection) for egress traffic.
|
||||
|
|
|
|||
|
|
@ -170,7 +170,7 @@ In the following subsections we configure a `Gateway` on port 80 for unencrypted
|
|||
configuration for the `httpbin` service, containing two route rules that allow traffic for paths `/status` and
|
||||
`/delay`.
|
||||
|
||||
The [gateways](/docs/reference/config/istio.networking.v1alpha3/#VirtualService.gateways) list
|
||||
The [gateways](/docs/reference/config/istio.networking.v1alpha3/#VirtualService-gateways) list
|
||||
specifies that only requests through our `httpbin-gateway` are allowed.
|
||||
All other external requests will be rejected with a 404 response.
|
||||
|
||||
|
|
|
|||
|
|
@ -247,4 +247,4 @@ Let's set up a scenario to demonstrate the traffic-mirroring capabilities of Ist
|
|||
|
||||
## What's next
|
||||
|
||||
Check out the [Mirroring configuration](/docs/reference/config/istio.networking.v1alpha3/#HTTPRoute.mirror) reference documentation.
|
||||
Check out the [Mirroring configuration](/docs/reference/config/istio.networking.v1alpha3/#HTTPRoute-mirror) reference documentation.
|
||||
|
|
|
|||
|
|
@ -60,13 +60,13 @@ get_command_doc() {
|
|||
# First delete all the current generated files so that any stale files are removed
|
||||
find _docs/reference -name '*.html' -type f|xargs rm
|
||||
|
||||
for f in `find ../api -type f -name '*.pb.html'`
|
||||
for f in `find $WORK_DIR/istio -type f -name '*.pb.html'`
|
||||
do
|
||||
echo "processing $f"
|
||||
locate_file $f
|
||||
done
|
||||
|
||||
for f in `find ../istio -type f -name '*.pb.html'`
|
||||
for f in `find $WORK_DIR/api -type f -name '*.pb.html'`
|
||||
do
|
||||
echo "processing $f"
|
||||
locate_file $f
|
||||
|
|
|
|||
Loading…
Reference in New Issue