mirror of https://github.com/istio/istio.io.git
Automator: update istio.io@ reference docs (#14917)
This commit is contained in:
Istio Automation
GitHub
parent
114f75af9e
commit
622b16d508
|
|
@ -1118,10 +1118,10 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If true, pilot will add Istio ALPN filters, required for proper protocol sniffing.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_AMBIENT_CONTROLLERS</code></td>
|
||||
<td><code>PILOT_ENABLE_AMBIENT</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, controllers required for ambient will run. This is required to run ambient mesh.</td>
|
||||
<td>If enabled, ambient mode can be used. Individual flags configure fine grained enablement; this must be enabled for any ambient functionality.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_AMBIENT_WAYPOINTS</code></td>
|
||||
|
|
@ -1190,12 +1190,6 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If this is set to true, gateway-api resources will have status written to them</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE support can be configured for proxies. Note: proxies must opt in on a per-proxy basis with ENABLE_HBONE to actually get HBONE config, in addition to this flag.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_K8S_SELECT_WORKLOAD_ENTRIES</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
|
|
@ -1256,12 +1250,24 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If true, Pilot will merge virtual hosts with the same routes into a single virtual host, as an optimization.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SENDING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE will be allowed when sending to destinations.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SERVICEENTRY_SELECT_PODS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
<td>If enabled, service entries with selectors will select pods from the cluster. It is safe to disable it if you are quite sure you don't need this feature</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SIDECAR_LISTENING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE support can be configured for proxies.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_STATUS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
|
|
@ -1376,6 +1382,12 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If not empty, services with this label will use cookie based persistent sessions</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_PREFER_SENDING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE will be preferred when sending to destinations. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_PUSH_THROTTLE</code></td>
|
||||
<td>Integer</td>
|
||||
<td><code>0</code></td>
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load Diff
|
|
@ -18,86 +18,10 @@ remove_toc_prefix: 'operator '
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--all-features</code></td>
|
||||
<td>Whether to enable all supported features for conformance tests </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--allow-crds-mismatch</code></td>
|
||||
<td>Flag to allow the suite not to fail in case there is a mismatch between CRDs versions and channels. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--cleanup-base-resources</code></td>
|
||||
<td>Whether to cleanup base test resources after the run </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--conformance-profiles <string></code></td>
|
||||
<td>Comma-separated list of the conformance profiles to run (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--contact <string></code></td>
|
||||
<td>Comma-separated list of contact information for the maintainers (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--debug</code></td>
|
||||
<td>Whether to print debug logs </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--exempt-features <string></code></td>
|
||||
<td>Exempt Features excluded from conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--gateway-class <string></code></td>
|
||||
<td>Name of GatewayClass to use for tests (default `gateway-conformance`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td>Paths to a kubeconfig. Only required if out-of-cluster. (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--mode <string></code></td>
|
||||
<td>The operating mode of the implementation. (default `default`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-annotations <string></code></td>
|
||||
<td>Comma-separated list of name=value annotations to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-labels <string></code></td>
|
||||
<td>Comma-separated list of name=value labels to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--organization <string></code></td>
|
||||
<td>Implementation's Organization (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--project <string></code></td>
|
||||
<td>Implementation's project (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--report-output <string></code></td>
|
||||
<td>The file where to write the conformance report (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--run-test <string></code></td>
|
||||
<td>Name of a single test to run, instead of the whole suite (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--skip-tests <string></code></td>
|
||||
<td>Comma-separated list of tests to skip (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--supported-features <string></code></td>
|
||||
<td>Supported features included in conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--url <string></code></td>
|
||||
<td>Implementation's url (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--version <string></code></td>
|
||||
<td>Implementation's version (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--vklog <Level></code></td>
|
||||
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9 (default `0`)</td>
|
||||
</tr>
|
||||
|
|
@ -116,86 +40,10 @@ See each sub-command's help for details on how to use the generated script.
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--all-features</code></td>
|
||||
<td>Whether to enable all supported features for conformance tests </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--allow-crds-mismatch</code></td>
|
||||
<td>Flag to allow the suite not to fail in case there is a mismatch between CRDs versions and channels. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--cleanup-base-resources</code></td>
|
||||
<td>Whether to cleanup base test resources after the run </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--conformance-profiles <string></code></td>
|
||||
<td>Comma-separated list of the conformance profiles to run (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--contact <string></code></td>
|
||||
<td>Comma-separated list of contact information for the maintainers (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--debug</code></td>
|
||||
<td>Whether to print debug logs </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--exempt-features <string></code></td>
|
||||
<td>Exempt Features excluded from conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--gateway-class <string></code></td>
|
||||
<td>Name of GatewayClass to use for tests (default `gateway-conformance`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td>Paths to a kubeconfig. Only required if out-of-cluster. (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--mode <string></code></td>
|
||||
<td>The operating mode of the implementation. (default `default`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-annotations <string></code></td>
|
||||
<td>Comma-separated list of name=value annotations to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-labels <string></code></td>
|
||||
<td>Comma-separated list of name=value labels to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--organization <string></code></td>
|
||||
<td>Implementation's Organization (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--project <string></code></td>
|
||||
<td>Implementation's project (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--report-output <string></code></td>
|
||||
<td>The file where to write the conformance report (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--run-test <string></code></td>
|
||||
<td>Name of a single test to run, instead of the whole suite (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--skip-tests <string></code></td>
|
||||
<td>Comma-separated list of tests to skip (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--supported-features <string></code></td>
|
||||
<td>Supported features included in conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--url <string></code></td>
|
||||
<td>Implementation's url (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--version <string></code></td>
|
||||
<td>Implementation's version (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--vklog <Level></code></td>
|
||||
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9 (default `0`)</td>
|
||||
</tr>
|
||||
|
|
@ -225,90 +73,14 @@ If it is not installed already, you can install it via your OS's package man
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--all-features</code></td>
|
||||
<td>Whether to enable all supported features for conformance tests </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--allow-crds-mismatch</code></td>
|
||||
<td>Flag to allow the suite not to fail in case there is a mismatch between CRDs versions and channels. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--cleanup-base-resources</code></td>
|
||||
<td>Whether to cleanup base test resources after the run </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--conformance-profiles <string></code></td>
|
||||
<td>Comma-separated list of the conformance profiles to run (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--contact <string></code></td>
|
||||
<td>Comma-separated list of contact information for the maintainers (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--debug</code></td>
|
||||
<td>Whether to print debug logs </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--exempt-features <string></code></td>
|
||||
<td>Exempt Features excluded from conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--gateway-class <string></code></td>
|
||||
<td>Name of GatewayClass to use for tests (default `gateway-conformance`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td>Paths to a kubeconfig. Only required if out-of-cluster. (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--mode <string></code></td>
|
||||
<td>The operating mode of the implementation. (default `default`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-annotations <string></code></td>
|
||||
<td>Comma-separated list of name=value annotations to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-labels <string></code></td>
|
||||
<td>Comma-separated list of name=value labels to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--no-descriptions</code></td>
|
||||
<td>disable completion descriptions </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--organization <string></code></td>
|
||||
<td>Implementation's Organization (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--project <string></code></td>
|
||||
<td>Implementation's project (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--report-output <string></code></td>
|
||||
<td>The file where to write the conformance report (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--run-test <string></code></td>
|
||||
<td>Name of a single test to run, instead of the whole suite (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--skip-tests <string></code></td>
|
||||
<td>Comma-separated list of tests to skip (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--supported-features <string></code></td>
|
||||
<td>Supported features included in conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--url <string></code></td>
|
||||
<td>Implementation's url (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--version <string></code></td>
|
||||
<td>Implementation's version (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--vklog <Level></code></td>
|
||||
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9 (default `0`)</td>
|
||||
</tr>
|
||||
|
|
@ -333,90 +105,14 @@ If it is not installed already, you can install it via your OS's package man
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--all-features</code></td>
|
||||
<td>Whether to enable all supported features for conformance tests </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--allow-crds-mismatch</code></td>
|
||||
<td>Flag to allow the suite not to fail in case there is a mismatch between CRDs versions and channels. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--cleanup-base-resources</code></td>
|
||||
<td>Whether to cleanup base test resources after the run </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--conformance-profiles <string></code></td>
|
||||
<td>Comma-separated list of the conformance profiles to run (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--contact <string></code></td>
|
||||
<td>Comma-separated list of contact information for the maintainers (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--debug</code></td>
|
||||
<td>Whether to print debug logs </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--exempt-features <string></code></td>
|
||||
<td>Exempt Features excluded from conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--gateway-class <string></code></td>
|
||||
<td>Name of GatewayClass to use for tests (default `gateway-conformance`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td>Paths to a kubeconfig. Only required if out-of-cluster. (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--mode <string></code></td>
|
||||
<td>The operating mode of the implementation. (default `default`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-annotations <string></code></td>
|
||||
<td>Comma-separated list of name=value annotations to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-labels <string></code></td>
|
||||
<td>Comma-separated list of name=value labels to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--no-descriptions</code></td>
|
||||
<td>disable completion descriptions </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--organization <string></code></td>
|
||||
<td>Implementation's Organization (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--project <string></code></td>
|
||||
<td>Implementation's project (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--report-output <string></code></td>
|
||||
<td>The file where to write the conformance report (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--run-test <string></code></td>
|
||||
<td>Name of a single test to run, instead of the whole suite (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--skip-tests <string></code></td>
|
||||
<td>Comma-separated list of tests to skip (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--supported-features <string></code></td>
|
||||
<td>Supported features included in conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--url <string></code></td>
|
||||
<td>Implementation's url (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--version <string></code></td>
|
||||
<td>Implementation's version (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--vklog <Level></code></td>
|
||||
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9 (default `0`)</td>
|
||||
</tr>
|
||||
|
|
@ -440,90 +136,14 @@ to your powershell profile.
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--all-features</code></td>
|
||||
<td>Whether to enable all supported features for conformance tests </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--allow-crds-mismatch</code></td>
|
||||
<td>Flag to allow the suite not to fail in case there is a mismatch between CRDs versions and channels. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--cleanup-base-resources</code></td>
|
||||
<td>Whether to cleanup base test resources after the run </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--conformance-profiles <string></code></td>
|
||||
<td>Comma-separated list of the conformance profiles to run (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--contact <string></code></td>
|
||||
<td>Comma-separated list of contact information for the maintainers (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--debug</code></td>
|
||||
<td>Whether to print debug logs </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--exempt-features <string></code></td>
|
||||
<td>Exempt Features excluded from conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--gateway-class <string></code></td>
|
||||
<td>Name of GatewayClass to use for tests (default `gateway-conformance`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td>Paths to a kubeconfig. Only required if out-of-cluster. (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--mode <string></code></td>
|
||||
<td>The operating mode of the implementation. (default `default`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-annotations <string></code></td>
|
||||
<td>Comma-separated list of name=value annotations to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-labels <string></code></td>
|
||||
<td>Comma-separated list of name=value labels to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--no-descriptions</code></td>
|
||||
<td>disable completion descriptions </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--organization <string></code></td>
|
||||
<td>Implementation's Organization (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--project <string></code></td>
|
||||
<td>Implementation's project (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--report-output <string></code></td>
|
||||
<td>The file where to write the conformance report (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--run-test <string></code></td>
|
||||
<td>Name of a single test to run, instead of the whole suite (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--skip-tests <string></code></td>
|
||||
<td>Comma-separated list of tests to skip (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--supported-features <string></code></td>
|
||||
<td>Supported features included in conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--url <string></code></td>
|
||||
<td>Implementation's url (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--version <string></code></td>
|
||||
<td>Implementation's version (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--vklog <Level></code></td>
|
||||
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9 (default `0`)</td>
|
||||
</tr>
|
||||
|
|
@ -554,90 +174,14 @@ to enable it. You can execute the following once:</p>
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--all-features</code></td>
|
||||
<td>Whether to enable all supported features for conformance tests </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--allow-crds-mismatch</code></td>
|
||||
<td>Flag to allow the suite not to fail in case there is a mismatch between CRDs versions and channels. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--cleanup-base-resources</code></td>
|
||||
<td>Whether to cleanup base test resources after the run </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--conformance-profiles <string></code></td>
|
||||
<td>Comma-separated list of the conformance profiles to run (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--contact <string></code></td>
|
||||
<td>Comma-separated list of contact information for the maintainers (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--debug</code></td>
|
||||
<td>Whether to print debug logs </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--exempt-features <string></code></td>
|
||||
<td>Exempt Features excluded from conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--gateway-class <string></code></td>
|
||||
<td>Name of GatewayClass to use for tests (default `gateway-conformance`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td>Paths to a kubeconfig. Only required if out-of-cluster. (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--mode <string></code></td>
|
||||
<td>The operating mode of the implementation. (default `default`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-annotations <string></code></td>
|
||||
<td>Comma-separated list of name=value annotations to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-labels <string></code></td>
|
||||
<td>Comma-separated list of name=value labels to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--no-descriptions</code></td>
|
||||
<td>disable completion descriptions </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--organization <string></code></td>
|
||||
<td>Implementation's Organization (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--project <string></code></td>
|
||||
<td>Implementation's project (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--report-output <string></code></td>
|
||||
<td>The file where to write the conformance report (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--run-test <string></code></td>
|
||||
<td>Name of a single test to run, instead of the whole suite (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--skip-tests <string></code></td>
|
||||
<td>Comma-separated list of tests to skip (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--supported-features <string></code></td>
|
||||
<td>Supported features included in conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--url <string></code></td>
|
||||
<td>Implementation's url (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--version <string></code></td>
|
||||
<td>Implementation's version (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--vklog <Level></code></td>
|
||||
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9 (default `0`)</td>
|
||||
</tr>
|
||||
|
|
@ -656,26 +200,6 @@ to enable it. You can execute the following once:</p>
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--all-features</code></td>
|
||||
<td>Whether to enable all supported features for conformance tests </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--allow-crds-mismatch</code></td>
|
||||
<td>Flag to allow the suite not to fail in case there is a mismatch between CRDs versions and channels. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--cleanup-base-resources</code></td>
|
||||
<td>Whether to cleanup base test resources after the run </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--conformance-profiles <string></code></td>
|
||||
<td>Comma-separated list of the conformance profiles to run (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--contact <string></code></td>
|
||||
<td>Comma-separated list of contact information for the maintainers (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--ctrlz_address <string></code></td>
|
||||
<td>The IP Address to listen on for the ControlZ introspection facility. Use '*' to indicate all addresses. (default `localhost`)</td>
|
||||
</tr>
|
||||
|
|
@ -684,22 +208,10 @@ to enable it. You can execute the following once:</p>
|
|||
<td>The IP port to use for the ControlZ introspection facility (default `9876`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--debug</code></td>
|
||||
<td>Whether to print debug logs </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--exempt-features <string></code></td>
|
||||
<td>Exempt Features excluded from conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--force</code></td>
|
||||
<td>Proceed even with validation errors. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--gateway-class <string></code></td>
|
||||
<td>Name of GatewayClass to use for tests (default `gateway-conformance`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td>Paths to a kubeconfig. Only required if out-of-cluster. (default ``)</td>
|
||||
</tr>
|
||||
|
|
@ -744,10 +256,6 @@ to enable it. You can execute the following once:</p>
|
|||
<td>Defines the concurrency limit for operator to reconcile IstioOperatorSpec in parallel. Default value is 1. (default `1`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--mode <string></code></td>
|
||||
<td>The operating mode of the implementation. (default `default`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--monitoring-host <string></code></td>
|
||||
<td>HTTP host to use for operator's self-monitoring information (default `0.0.0.0`)</td>
|
||||
</tr>
|
||||
|
|
@ -756,46 +264,6 @@ to enable it. You can execute the following once:</p>
|
|||
<td>HTTP port to use for operator's self-monitoring information (default `8383`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-annotations <string></code></td>
|
||||
<td>Comma-separated list of name=value annotations to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-labels <string></code></td>
|
||||
<td>Comma-separated list of name=value labels to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--organization <string></code></td>
|
||||
<td>Implementation's Organization (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--project <string></code></td>
|
||||
<td>Implementation's project (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--report-output <string></code></td>
|
||||
<td>The file where to write the conformance report (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--run-test <string></code></td>
|
||||
<td>Name of a single test to run, instead of the whole suite (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--skip-tests <string></code></td>
|
||||
<td>Comma-separated list of tests to skip (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--supported-features <string></code></td>
|
||||
<td>Supported features included in conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--url <string></code></td>
|
||||
<td>Implementation's url (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--version <string></code></td>
|
||||
<td>Implementation's version (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--vklog <Level></code></td>
|
||||
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9 (default `0`)</td>
|
||||
</tr>
|
||||
|
|
@ -815,116 +283,21 @@ to enable it. You can execute the following once:</p>
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--all-features</code></td>
|
||||
<td></td>
|
||||
<td>Whether to enable all supported features for conformance tests </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--allow-crds-mismatch</code></td>
|
||||
<td></td>
|
||||
<td>Flag to allow the suite not to fail in case there is a mismatch between CRDs versions and channels. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--cleanup-base-resources</code></td>
|
||||
<td></td>
|
||||
<td>Whether to cleanup base test resources after the run </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--conformance-profiles <string></code></td>
|
||||
<td></td>
|
||||
<td>Comma-separated list of the conformance profiles to run (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--contact <string></code></td>
|
||||
<td></td>
|
||||
<td>Comma-separated list of contact information for the maintainers (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--debug</code></td>
|
||||
<td></td>
|
||||
<td>Whether to print debug logs </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--exempt-features <string></code></td>
|
||||
<td></td>
|
||||
<td>Exempt Features excluded from conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--gateway-class <string></code></td>
|
||||
<td></td>
|
||||
<td>Name of GatewayClass to use for tests (default `gateway-conformance`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td></td>
|
||||
<td>Paths to a kubeconfig. Only required if out-of-cluster. (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--mode <string></code></td>
|
||||
<td></td>
|
||||
<td>The operating mode of the implementation. (default `default`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-annotations <string></code></td>
|
||||
<td></td>
|
||||
<td>Comma-separated list of name=value annotations to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-labels <string></code></td>
|
||||
<td></td>
|
||||
<td>Comma-separated list of name=value labels to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--organization <string></code></td>
|
||||
<td></td>
|
||||
<td>Implementation's Organization (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--output <string></code></td>
|
||||
<td><code>-o</code></td>
|
||||
<td>One of 'yaml' or 'json'. (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--project <string></code></td>
|
||||
<td></td>
|
||||
<td>Implementation's project (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--report-output <string></code></td>
|
||||
<td></td>
|
||||
<td>The file where to write the conformance report (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--run-test <string></code></td>
|
||||
<td></td>
|
||||
<td>Name of a single test to run, instead of the whole suite (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--short</code></td>
|
||||
<td><code>-s</code></td>
|
||||
<td>Use --short=false to generate full version information </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--skip-tests <string></code></td>
|
||||
<td></td>
|
||||
<td>Comma-separated list of tests to skip (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--supported-features <string></code></td>
|
||||
<td></td>
|
||||
<td>Supported features included in conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--url <string></code></td>
|
||||
<td></td>
|
||||
<td>Implementation's url (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--version <string></code></td>
|
||||
<td></td>
|
||||
<td>Implementation's version (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--vklog <Level></code></td>
|
||||
<td></td>
|
||||
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9 (default `0`)</td>
|
||||
|
|
@ -1404,10 +777,10 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If true, pilot will add Istio ALPN filters, required for proper protocol sniffing.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_AMBIENT_CONTROLLERS</code></td>
|
||||
<td><code>PILOT_ENABLE_AMBIENT</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, controllers required for ambient will run. This is required to run ambient mesh.</td>
|
||||
<td>If enabled, ambient mode can be used. Individual flags configure fine grained enablement; this must be enabled for any ambient functionality.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_AMBIENT_WAYPOINTS</code></td>
|
||||
|
|
@ -1476,12 +849,6 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If this is set to true, gateway-api resources will have status written to them</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE support can be configured for proxies. Note: proxies must opt in on a per-proxy basis with ENABLE_HBONE to actually get HBONE config, in addition to this flag.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_K8S_SELECT_WORKLOAD_ENTRIES</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
|
|
@ -1542,12 +909,24 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If true, Pilot will merge virtual hosts with the same routes into a single virtual host, as an optimization.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SENDING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE will be allowed when sending to destinations.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SERVICEENTRY_SELECT_PODS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
<td>If enabled, service entries with selectors will select pods from the cluster. It is safe to disable it if you are quite sure you don't need this feature</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SIDECAR_LISTENING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE support can be configured for proxies.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_STATUS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
|
|
@ -1662,6 +1041,12 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If not empty, services with this label will use cookie based persistent sessions</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_PREFER_SENDING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE will be preferred when sending to destinations. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_PUSH_THROTTLE</code></td>
|
||||
<td>Integer</td>
|
||||
<td><code>0</code></td>
|
||||
|
|
|
|||
|
|
@ -1667,10 +1667,10 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If true, pilot will add Istio ALPN filters, required for proper protocol sniffing.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_AMBIENT_CONTROLLERS</code></td>
|
||||
<td><code>PILOT_ENABLE_AMBIENT</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, controllers required for ambient will run. This is required to run ambient mesh.</td>
|
||||
<td>If enabled, ambient mode can be used. Individual flags configure fine grained enablement; this must be enabled for any ambient functionality.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_AMBIENT_WAYPOINTS</code></td>
|
||||
|
|
@ -1739,12 +1739,6 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If this is set to true, gateway-api resources will have status written to them</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE support can be configured for proxies. Note: proxies must opt in on a per-proxy basis with ENABLE_HBONE to actually get HBONE config, in addition to this flag.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_K8S_SELECT_WORKLOAD_ENTRIES</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
|
|
@ -1805,12 +1799,24 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If true, Pilot will merge virtual hosts with the same routes into a single virtual host, as an optimization.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SENDING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE will be allowed when sending to destinations.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SERVICEENTRY_SELECT_PODS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
<td>If enabled, service entries with selectors will select pods from the cluster. It is safe to disable it if you are quite sure you don't need this feature</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SIDECAR_LISTENING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE support can be configured for proxies.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_STATUS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
|
|
@ -1925,6 +1931,12 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If not empty, services with this label will use cookie based persistent sessions</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_PREFER_SENDING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE will be preferred when sending to destinations. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_PUSH_THROTTLE</code></td>
|
||||
<td>Integer</td>
|
||||
<td><code>0</code></td>
|
||||
|
|
|
|||
|
|
@ -980,10 +980,10 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If true, pilot will add Istio ALPN filters, required for proper protocol sniffing.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_AMBIENT_CONTROLLERS</code></td>
|
||||
<td><code>PILOT_ENABLE_AMBIENT</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, controllers required for ambient will run. This is required to run ambient mesh.</td>
|
||||
<td>If enabled, ambient mode can be used. Individual flags configure fine grained enablement; this must be enabled for any ambient functionality.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_AMBIENT_WAYPOINTS</code></td>
|
||||
|
|
@ -1052,12 +1052,6 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If this is set to true, gateway-api resources will have status written to them</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE support can be configured for proxies. Note: proxies must opt in on a per-proxy basis with ENABLE_HBONE to actually get HBONE config, in addition to this flag.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_K8S_SELECT_WORKLOAD_ENTRIES</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
|
|
@ -1118,12 +1112,24 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If true, Pilot will merge virtual hosts with the same routes into a single virtual host, as an optimization.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SENDING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE will be allowed when sending to destinations.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SERVICEENTRY_SELECT_PODS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
<td>If enabled, service entries with selectors will select pods from the cluster. It is safe to disable it if you are quite sure you don't need this feature</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SIDECAR_LISTENING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE support can be configured for proxies.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_STATUS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
|
|
@ -1238,6 +1244,12 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If not empty, services with this label will use cookie based persistent sessions</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_PREFER_SENDING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE will be preferred when sending to destinations. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_PUSH_THROTTLE</code></td>
|
||||
<td>Integer</td>
|
||||
<td><code>0</code></td>
|
||||
|
|
|
|||
|
|
@ -1118,10 +1118,10 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If true, pilot will add Istio ALPN filters, required for proper protocol sniffing.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_AMBIENT_CONTROLLERS</code></td>
|
||||
<td><code>PILOT_ENABLE_AMBIENT</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, controllers required for ambient will run. This is required to run ambient mesh.</td>
|
||||
<td>If enabled, ambient mode can be used. Individual flags configure fine grained enablement; this must be enabled for any ambient functionality.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_AMBIENT_WAYPOINTS</code></td>
|
||||
|
|
@ -1190,12 +1190,6 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If this is set to true, gateway-api resources will have status written to them</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE support can be configured for proxies. Note: proxies must opt in on a per-proxy basis with ENABLE_HBONE to actually get HBONE config, in addition to this flag.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_K8S_SELECT_WORKLOAD_ENTRIES</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
|
|
@ -1256,12 +1250,24 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If true, Pilot will merge virtual hosts with the same routes into a single virtual host, as an optimization.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SENDING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE will be allowed when sending to destinations.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SERVICEENTRY_SELECT_PODS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
<td>If enabled, service entries with selectors will select pods from the cluster. It is safe to disable it if you are quite sure you don't need this feature</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SIDECAR_LISTENING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE support can be configured for proxies.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_STATUS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
|
|
@ -1376,6 +1382,12 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If not empty, services with this label will use cookie based persistent sessions</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_PREFER_SENDING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE will be preferred when sending to destinations. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_PUSH_THROTTLE</code></td>
|
||||
<td>Integer</td>
|
||||
<td><code>0</code></td>
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load Diff
|
|
@ -18,86 +18,10 @@ remove_toc_prefix: 'operator '
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--all-features</code></td>
|
||||
<td>Whether to enable all supported features for conformance tests </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--allow-crds-mismatch</code></td>
|
||||
<td>Flag to allow the suite not to fail in case there is a mismatch between CRDs versions and channels. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--cleanup-base-resources</code></td>
|
||||
<td>Whether to cleanup base test resources after the run </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--conformance-profiles <string></code></td>
|
||||
<td>Comma-separated list of the conformance profiles to run (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--contact <string></code></td>
|
||||
<td>Comma-separated list of contact information for the maintainers (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--debug</code></td>
|
||||
<td>Whether to print debug logs </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--exempt-features <string></code></td>
|
||||
<td>Exempt Features excluded from conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--gateway-class <string></code></td>
|
||||
<td>Name of GatewayClass to use for tests (default `gateway-conformance`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td>Paths to a kubeconfig. Only required if out-of-cluster. (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--mode <string></code></td>
|
||||
<td>The operating mode of the implementation. (default `default`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-annotations <string></code></td>
|
||||
<td>Comma-separated list of name=value annotations to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-labels <string></code></td>
|
||||
<td>Comma-separated list of name=value labels to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--organization <string></code></td>
|
||||
<td>Implementation's Organization (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--project <string></code></td>
|
||||
<td>Implementation's project (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--report-output <string></code></td>
|
||||
<td>The file where to write the conformance report (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--run-test <string></code></td>
|
||||
<td>Name of a single test to run, instead of the whole suite (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--skip-tests <string></code></td>
|
||||
<td>Comma-separated list of tests to skip (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--supported-features <string></code></td>
|
||||
<td>Supported features included in conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--url <string></code></td>
|
||||
<td>Implementation's url (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--version <string></code></td>
|
||||
<td>Implementation's version (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--vklog <Level></code></td>
|
||||
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9 (default `0`)</td>
|
||||
</tr>
|
||||
|
|
@ -116,86 +40,10 @@ See each sub-command's help for details on how to use the generated script.
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--all-features</code></td>
|
||||
<td>Whether to enable all supported features for conformance tests </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--allow-crds-mismatch</code></td>
|
||||
<td>Flag to allow the suite not to fail in case there is a mismatch between CRDs versions and channels. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--cleanup-base-resources</code></td>
|
||||
<td>Whether to cleanup base test resources after the run </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--conformance-profiles <string></code></td>
|
||||
<td>Comma-separated list of the conformance profiles to run (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--contact <string></code></td>
|
||||
<td>Comma-separated list of contact information for the maintainers (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--debug</code></td>
|
||||
<td>Whether to print debug logs </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--exempt-features <string></code></td>
|
||||
<td>Exempt Features excluded from conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--gateway-class <string></code></td>
|
||||
<td>Name of GatewayClass to use for tests (default `gateway-conformance`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td>Paths to a kubeconfig. Only required if out-of-cluster. (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--mode <string></code></td>
|
||||
<td>The operating mode of the implementation. (default `default`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-annotations <string></code></td>
|
||||
<td>Comma-separated list of name=value annotations to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-labels <string></code></td>
|
||||
<td>Comma-separated list of name=value labels to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--organization <string></code></td>
|
||||
<td>Implementation's Organization (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--project <string></code></td>
|
||||
<td>Implementation's project (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--report-output <string></code></td>
|
||||
<td>The file where to write the conformance report (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--run-test <string></code></td>
|
||||
<td>Name of a single test to run, instead of the whole suite (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--skip-tests <string></code></td>
|
||||
<td>Comma-separated list of tests to skip (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--supported-features <string></code></td>
|
||||
<td>Supported features included in conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--url <string></code></td>
|
||||
<td>Implementation's url (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--version <string></code></td>
|
||||
<td>Implementation's version (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--vklog <Level></code></td>
|
||||
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9 (default `0`)</td>
|
||||
</tr>
|
||||
|
|
@ -225,90 +73,14 @@ If it is not installed already, you can install it via your OS's package man
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--all-features</code></td>
|
||||
<td>Whether to enable all supported features for conformance tests </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--allow-crds-mismatch</code></td>
|
||||
<td>Flag to allow the suite not to fail in case there is a mismatch between CRDs versions and channels. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--cleanup-base-resources</code></td>
|
||||
<td>Whether to cleanup base test resources after the run </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--conformance-profiles <string></code></td>
|
||||
<td>Comma-separated list of the conformance profiles to run (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--contact <string></code></td>
|
||||
<td>Comma-separated list of contact information for the maintainers (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--debug</code></td>
|
||||
<td>Whether to print debug logs </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--exempt-features <string></code></td>
|
||||
<td>Exempt Features excluded from conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--gateway-class <string></code></td>
|
||||
<td>Name of GatewayClass to use for tests (default `gateway-conformance`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td>Paths to a kubeconfig. Only required if out-of-cluster. (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--mode <string></code></td>
|
||||
<td>The operating mode of the implementation. (default `default`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-annotations <string></code></td>
|
||||
<td>Comma-separated list of name=value annotations to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-labels <string></code></td>
|
||||
<td>Comma-separated list of name=value labels to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--no-descriptions</code></td>
|
||||
<td>disable completion descriptions </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--organization <string></code></td>
|
||||
<td>Implementation's Organization (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--project <string></code></td>
|
||||
<td>Implementation's project (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--report-output <string></code></td>
|
||||
<td>The file where to write the conformance report (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--run-test <string></code></td>
|
||||
<td>Name of a single test to run, instead of the whole suite (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--skip-tests <string></code></td>
|
||||
<td>Comma-separated list of tests to skip (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--supported-features <string></code></td>
|
||||
<td>Supported features included in conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--url <string></code></td>
|
||||
<td>Implementation's url (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--version <string></code></td>
|
||||
<td>Implementation's version (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--vklog <Level></code></td>
|
||||
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9 (default `0`)</td>
|
||||
</tr>
|
||||
|
|
@ -333,90 +105,14 @@ If it is not installed already, you can install it via your OS's package man
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--all-features</code></td>
|
||||
<td>Whether to enable all supported features for conformance tests </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--allow-crds-mismatch</code></td>
|
||||
<td>Flag to allow the suite not to fail in case there is a mismatch between CRDs versions and channels. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--cleanup-base-resources</code></td>
|
||||
<td>Whether to cleanup base test resources after the run </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--conformance-profiles <string></code></td>
|
||||
<td>Comma-separated list of the conformance profiles to run (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--contact <string></code></td>
|
||||
<td>Comma-separated list of contact information for the maintainers (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--debug</code></td>
|
||||
<td>Whether to print debug logs </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--exempt-features <string></code></td>
|
||||
<td>Exempt Features excluded from conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--gateway-class <string></code></td>
|
||||
<td>Name of GatewayClass to use for tests (default `gateway-conformance`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td>Paths to a kubeconfig. Only required if out-of-cluster. (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--mode <string></code></td>
|
||||
<td>The operating mode of the implementation. (default `default`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-annotations <string></code></td>
|
||||
<td>Comma-separated list of name=value annotations to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-labels <string></code></td>
|
||||
<td>Comma-separated list of name=value labels to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--no-descriptions</code></td>
|
||||
<td>disable completion descriptions </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--organization <string></code></td>
|
||||
<td>Implementation's Organization (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--project <string></code></td>
|
||||
<td>Implementation's project (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--report-output <string></code></td>
|
||||
<td>The file where to write the conformance report (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--run-test <string></code></td>
|
||||
<td>Name of a single test to run, instead of the whole suite (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--skip-tests <string></code></td>
|
||||
<td>Comma-separated list of tests to skip (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--supported-features <string></code></td>
|
||||
<td>Supported features included in conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--url <string></code></td>
|
||||
<td>Implementation's url (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--version <string></code></td>
|
||||
<td>Implementation's version (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--vklog <Level></code></td>
|
||||
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9 (default `0`)</td>
|
||||
</tr>
|
||||
|
|
@ -440,90 +136,14 @@ to your powershell profile.
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--all-features</code></td>
|
||||
<td>Whether to enable all supported features for conformance tests </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--allow-crds-mismatch</code></td>
|
||||
<td>Flag to allow the suite not to fail in case there is a mismatch between CRDs versions and channels. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--cleanup-base-resources</code></td>
|
||||
<td>Whether to cleanup base test resources after the run </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--conformance-profiles <string></code></td>
|
||||
<td>Comma-separated list of the conformance profiles to run (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--contact <string></code></td>
|
||||
<td>Comma-separated list of contact information for the maintainers (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--debug</code></td>
|
||||
<td>Whether to print debug logs </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--exempt-features <string></code></td>
|
||||
<td>Exempt Features excluded from conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--gateway-class <string></code></td>
|
||||
<td>Name of GatewayClass to use for tests (default `gateway-conformance`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td>Paths to a kubeconfig. Only required if out-of-cluster. (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--mode <string></code></td>
|
||||
<td>The operating mode of the implementation. (default `default`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-annotations <string></code></td>
|
||||
<td>Comma-separated list of name=value annotations to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-labels <string></code></td>
|
||||
<td>Comma-separated list of name=value labels to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--no-descriptions</code></td>
|
||||
<td>disable completion descriptions </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--organization <string></code></td>
|
||||
<td>Implementation's Organization (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--project <string></code></td>
|
||||
<td>Implementation's project (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--report-output <string></code></td>
|
||||
<td>The file where to write the conformance report (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--run-test <string></code></td>
|
||||
<td>Name of a single test to run, instead of the whole suite (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--skip-tests <string></code></td>
|
||||
<td>Comma-separated list of tests to skip (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--supported-features <string></code></td>
|
||||
<td>Supported features included in conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--url <string></code></td>
|
||||
<td>Implementation's url (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--version <string></code></td>
|
||||
<td>Implementation's version (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--vklog <Level></code></td>
|
||||
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9 (default `0`)</td>
|
||||
</tr>
|
||||
|
|
@ -554,90 +174,14 @@ to enable it. You can execute the following once:</p>
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--all-features</code></td>
|
||||
<td>Whether to enable all supported features for conformance tests </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--allow-crds-mismatch</code></td>
|
||||
<td>Flag to allow the suite not to fail in case there is a mismatch between CRDs versions and channels. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--cleanup-base-resources</code></td>
|
||||
<td>Whether to cleanup base test resources after the run </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--conformance-profiles <string></code></td>
|
||||
<td>Comma-separated list of the conformance profiles to run (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--contact <string></code></td>
|
||||
<td>Comma-separated list of contact information for the maintainers (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--debug</code></td>
|
||||
<td>Whether to print debug logs </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--exempt-features <string></code></td>
|
||||
<td>Exempt Features excluded from conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--gateway-class <string></code></td>
|
||||
<td>Name of GatewayClass to use for tests (default `gateway-conformance`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td>Paths to a kubeconfig. Only required if out-of-cluster. (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--mode <string></code></td>
|
||||
<td>The operating mode of the implementation. (default `default`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-annotations <string></code></td>
|
||||
<td>Comma-separated list of name=value annotations to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-labels <string></code></td>
|
||||
<td>Comma-separated list of name=value labels to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--no-descriptions</code></td>
|
||||
<td>disable completion descriptions </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--organization <string></code></td>
|
||||
<td>Implementation's Organization (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--project <string></code></td>
|
||||
<td>Implementation's project (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--report-output <string></code></td>
|
||||
<td>The file where to write the conformance report (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--run-test <string></code></td>
|
||||
<td>Name of a single test to run, instead of the whole suite (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--skip-tests <string></code></td>
|
||||
<td>Comma-separated list of tests to skip (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--supported-features <string></code></td>
|
||||
<td>Supported features included in conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--url <string></code></td>
|
||||
<td>Implementation's url (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--version <string></code></td>
|
||||
<td>Implementation's version (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--vklog <Level></code></td>
|
||||
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9 (default `0`)</td>
|
||||
</tr>
|
||||
|
|
@ -656,26 +200,6 @@ to enable it. You can execute the following once:</p>
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--all-features</code></td>
|
||||
<td>Whether to enable all supported features for conformance tests </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--allow-crds-mismatch</code></td>
|
||||
<td>Flag to allow the suite not to fail in case there is a mismatch between CRDs versions and channels. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--cleanup-base-resources</code></td>
|
||||
<td>Whether to cleanup base test resources after the run </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--conformance-profiles <string></code></td>
|
||||
<td>Comma-separated list of the conformance profiles to run (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--contact <string></code></td>
|
||||
<td>Comma-separated list of contact information for the maintainers (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--ctrlz_address <string></code></td>
|
||||
<td>The IP Address to listen on for the ControlZ introspection facility. Use '*' to indicate all addresses. (default `localhost`)</td>
|
||||
</tr>
|
||||
|
|
@ -684,22 +208,10 @@ to enable it. You can execute the following once:</p>
|
|||
<td>The IP port to use for the ControlZ introspection facility (default `9876`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--debug</code></td>
|
||||
<td>Whether to print debug logs </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--exempt-features <string></code></td>
|
||||
<td>Exempt Features excluded from conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--force</code></td>
|
||||
<td>Proceed even with validation errors. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--gateway-class <string></code></td>
|
||||
<td>Name of GatewayClass to use for tests (default `gateway-conformance`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td>Paths to a kubeconfig. Only required if out-of-cluster. (default ``)</td>
|
||||
</tr>
|
||||
|
|
@ -744,10 +256,6 @@ to enable it. You can execute the following once:</p>
|
|||
<td>Defines the concurrency limit for operator to reconcile IstioOperatorSpec in parallel. Default value is 1. (default `1`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--mode <string></code></td>
|
||||
<td>The operating mode of the implementation. (default `default`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--monitoring-host <string></code></td>
|
||||
<td>HTTP host to use for operator's self-monitoring information (default `0.0.0.0`)</td>
|
||||
</tr>
|
||||
|
|
@ -756,46 +264,6 @@ to enable it. You can execute the following once:</p>
|
|||
<td>HTTP port to use for operator's self-monitoring information (default `8383`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-annotations <string></code></td>
|
||||
<td>Comma-separated list of name=value annotations to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-labels <string></code></td>
|
||||
<td>Comma-separated list of name=value labels to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--organization <string></code></td>
|
||||
<td>Implementation's Organization (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--project <string></code></td>
|
||||
<td>Implementation's project (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--report-output <string></code></td>
|
||||
<td>The file where to write the conformance report (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--run-test <string></code></td>
|
||||
<td>Name of a single test to run, instead of the whole suite (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--skip-tests <string></code></td>
|
||||
<td>Comma-separated list of tests to skip (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--supported-features <string></code></td>
|
||||
<td>Supported features included in conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--url <string></code></td>
|
||||
<td>Implementation's url (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--version <string></code></td>
|
||||
<td>Implementation's version (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--vklog <Level></code></td>
|
||||
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9 (default `0`)</td>
|
||||
</tr>
|
||||
|
|
@ -815,116 +283,21 @@ to enable it. You can execute the following once:</p>
|
|||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>--all-features</code></td>
|
||||
<td></td>
|
||||
<td>Whether to enable all supported features for conformance tests </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--allow-crds-mismatch</code></td>
|
||||
<td></td>
|
||||
<td>Flag to allow the suite not to fail in case there is a mismatch between CRDs versions and channels. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--cleanup-base-resources</code></td>
|
||||
<td></td>
|
||||
<td>Whether to cleanup base test resources after the run </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--conformance-profiles <string></code></td>
|
||||
<td></td>
|
||||
<td>Comma-separated list of the conformance profiles to run (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--contact <string></code></td>
|
||||
<td></td>
|
||||
<td>Comma-separated list of contact information for the maintainers (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--debug</code></td>
|
||||
<td></td>
|
||||
<td>Whether to print debug logs </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--exempt-features <string></code></td>
|
||||
<td></td>
|
||||
<td>Exempt Features excluded from conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--gateway-class <string></code></td>
|
||||
<td></td>
|
||||
<td>Name of GatewayClass to use for tests (default `gateway-conformance`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--kubeconfig <string></code></td>
|
||||
<td></td>
|
||||
<td>Paths to a kubeconfig. Only required if out-of-cluster. (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--mode <string></code></td>
|
||||
<td></td>
|
||||
<td>The operating mode of the implementation. (default `default`)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-annotations <string></code></td>
|
||||
<td></td>
|
||||
<td>Comma-separated list of name=value annotations to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--namespace-labels <string></code></td>
|
||||
<td></td>
|
||||
<td>Comma-separated list of name=value labels to add to test namespaces (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--organization <string></code></td>
|
||||
<td></td>
|
||||
<td>Implementation's Organization (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--output <string></code></td>
|
||||
<td><code>-o</code></td>
|
||||
<td>One of 'yaml' or 'json'. (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--project <string></code></td>
|
||||
<td></td>
|
||||
<td>Implementation's project (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--report-output <string></code></td>
|
||||
<td></td>
|
||||
<td>The file where to write the conformance report (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--run-test <string></code></td>
|
||||
<td></td>
|
||||
<td>Name of a single test to run, instead of the whole suite (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--short</code></td>
|
||||
<td><code>-s</code></td>
|
||||
<td>Use --short=false to generate full version information </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--skip-tests <string></code></td>
|
||||
<td></td>
|
||||
<td>Comma-separated list of tests to skip (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--supported-features <string></code></td>
|
||||
<td></td>
|
||||
<td>Supported features included in conformance tests suites (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--url <string></code></td>
|
||||
<td></td>
|
||||
<td>Implementation's url (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--version <string></code></td>
|
||||
<td></td>
|
||||
<td>Implementation's version (default ``)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--vklog <Level></code></td>
|
||||
<td></td>
|
||||
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9 (default `0`)</td>
|
||||
|
|
@ -1404,10 +777,10 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If true, pilot will add Istio ALPN filters, required for proper protocol sniffing.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_AMBIENT_CONTROLLERS</code></td>
|
||||
<td><code>PILOT_ENABLE_AMBIENT</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, controllers required for ambient will run. This is required to run ambient mesh.</td>
|
||||
<td>If enabled, ambient mode can be used. Individual flags configure fine grained enablement; this must be enabled for any ambient functionality.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_AMBIENT_WAYPOINTS</code></td>
|
||||
|
|
@ -1476,12 +849,6 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If this is set to true, gateway-api resources will have status written to them</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE support can be configured for proxies. Note: proxies must opt in on a per-proxy basis with ENABLE_HBONE to actually get HBONE config, in addition to this flag.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_K8S_SELECT_WORKLOAD_ENTRIES</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
|
|
@ -1542,12 +909,24 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If true, Pilot will merge virtual hosts with the same routes into a single virtual host, as an optimization.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SENDING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE will be allowed when sending to destinations.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SERVICEENTRY_SELECT_PODS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
<td>If enabled, service entries with selectors will select pods from the cluster. It is safe to disable it if you are quite sure you don't need this feature</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SIDECAR_LISTENING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE support can be configured for proxies.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_STATUS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
|
|
@ -1662,6 +1041,12 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If not empty, services with this label will use cookie based persistent sessions</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_PREFER_SENDING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE will be preferred when sending to destinations. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_PUSH_THROTTLE</code></td>
|
||||
<td>Integer</td>
|
||||
<td><code>0</code></td>
|
||||
|
|
|
|||
|
|
@ -1667,10 +1667,10 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If true, pilot will add Istio ALPN filters, required for proper protocol sniffing.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_AMBIENT_CONTROLLERS</code></td>
|
||||
<td><code>PILOT_ENABLE_AMBIENT</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, controllers required for ambient will run. This is required to run ambient mesh.</td>
|
||||
<td>If enabled, ambient mode can be used. Individual flags configure fine grained enablement; this must be enabled for any ambient functionality.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_AMBIENT_WAYPOINTS</code></td>
|
||||
|
|
@ -1739,12 +1739,6 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If this is set to true, gateway-api resources will have status written to them</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE support can be configured for proxies. Note: proxies must opt in on a per-proxy basis with ENABLE_HBONE to actually get HBONE config, in addition to this flag.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_K8S_SELECT_WORKLOAD_ENTRIES</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
|
|
@ -1805,12 +1799,24 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If true, Pilot will merge virtual hosts with the same routes into a single virtual host, as an optimization.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SENDING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE will be allowed when sending to destinations.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SERVICEENTRY_SELECT_PODS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
<td>If enabled, service entries with selectors will select pods from the cluster. It is safe to disable it if you are quite sure you don't need this feature</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SIDECAR_LISTENING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE support can be configured for proxies.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_STATUS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
|
|
@ -1925,6 +1931,12 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If not empty, services with this label will use cookie based persistent sessions</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_PREFER_SENDING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE will be preferred when sending to destinations. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_PUSH_THROTTLE</code></td>
|
||||
<td>Integer</td>
|
||||
<td><code>0</code></td>
|
||||
|
|
|
|||
|
|
@ -980,10 +980,10 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If true, pilot will add Istio ALPN filters, required for proper protocol sniffing.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_AMBIENT_CONTROLLERS</code></td>
|
||||
<td><code>PILOT_ENABLE_AMBIENT</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, controllers required for ambient will run. This is required to run ambient mesh.</td>
|
||||
<td>If enabled, ambient mode can be used. Individual flags configure fine grained enablement; this must be enabled for any ambient functionality.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_AMBIENT_WAYPOINTS</code></td>
|
||||
|
|
@ -1052,12 +1052,6 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If this is set to true, gateway-api resources will have status written to them</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE support can be configured for proxies. Note: proxies must opt in on a per-proxy basis with ENABLE_HBONE to actually get HBONE config, in addition to this flag.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_K8S_SELECT_WORKLOAD_ENTRIES</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
|
|
@ -1118,12 +1112,24 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If true, Pilot will merge virtual hosts with the same routes into a single virtual host, as an optimization.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SENDING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE will be allowed when sending to destinations.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SERVICEENTRY_SELECT_PODS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
<td>If enabled, service entries with selectors will select pods from the cluster. It is safe to disable it if you are quite sure you don't need this feature</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_SIDECAR_LISTENING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE support can be configured for proxies.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_STATUS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
|
|
@ -1238,6 +1244,12 @@ Only applies when traffic from all groups (i.e. "*") is being redirected
|
|||
<td>If not empty, services with this label will use cookie based persistent sessions</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_PREFER_SENDING_HBONE</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>false</code></td>
|
||||
<td>If enabled, HBONE will be preferred when sending to destinations. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_PUSH_THROTTLE</code></td>
|
||||
<td>Integer</td>
|
||||
<td><code>0</code></td>
|
||||
|
|
|
|||
Loading…
Reference in New Issue