mirror of https://github.com/istio/istio.io.git
Automator: update istio.io@ reference docs (#16840)
This commit is contained in:
Istio Automation
GitHub
parent
39aabda08d
commit
ed0c5d73c9
|
|
@ -574,7 +574,7 @@ gRPC Go SDK, and gRPC C++ SDK. This policy is experimental.
|
|||
WARNING: Setting compliance policy in the control plane is a necessary but
|
||||
not a sufficient requirement to achieve compliance. There are additional
|
||||
steps necessary to claim compliance, including using the validated
|
||||
cryptograhic modules (please consult
|
||||
cryptographic modules (please consult
|
||||
https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ssl#fips-140-2).</td>
|
||||
</tr>
|
||||
<tr id='dry-run-file-path'>
|
||||
|
|
|
|||
|
|
@ -8520,7 +8520,7 @@ gRPC Go SDK, and gRPC C++ SDK. This policy is experimental.
|
|||
WARNING: Setting compliance policy in the control plane is a necessary but
|
||||
not a sufficient requirement to achieve compliance. There are additional
|
||||
steps necessary to claim compliance, including using the validated
|
||||
cryptograhic modules (please consult
|
||||
cryptographic modules (please consult
|
||||
https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ssl#fips-140-2).</td>
|
||||
</tr>
|
||||
<tr id='enable-100-continue-headers'>
|
||||
|
|
|
|||
|
|
@ -795,7 +795,7 @@ gRPC Go SDK, and gRPC C++ SDK. This policy is experimental.
|
|||
WARNING: Setting compliance policy in the control plane is a necessary but
|
||||
not a sufficient requirement to achieve compliance. There are additional
|
||||
steps necessary to claim compliance, including using the validated
|
||||
cryptograhic modules (please consult
|
||||
cryptographic modules (please consult
|
||||
https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ssl#fips-140-2).</td>
|
||||
</tr>
|
||||
<tr id='credential-fetcher-type'>
|
||||
|
|
|
|||
|
|
@ -500,7 +500,7 @@ gRPC Go SDK, and gRPC C++ SDK. This policy is experimental.
|
|||
WARNING: Setting compliance policy in the control plane is a necessary but
|
||||
not a sufficient requirement to achieve compliance. There are additional
|
||||
steps necessary to claim compliance, including using the validated
|
||||
cryptograhic modules (please consult
|
||||
cryptographic modules (please consult
|
||||
https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ssl#fips-140-2).</td>
|
||||
</tr>
|
||||
<tr id='default-workload-cert-ttl'>
|
||||
|
|
|
|||
|
|
@ -33,6 +33,28 @@ Istio supports to control its behavior.
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="IoK8sNetworkingGatewayGatewayClassName">gateway.networking.k8s.io/gateway-class-name</h2>
|
||||
<table class="annotations">
|
||||
<tbody>
|
||||
<tr>
|
||||
<th>Name</th>
|
||||
<td><code>gateway.networking.k8s.io/gateway-class-name</code></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th>Feature Status</th>
|
||||
<td>Stable</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th>Resource Types</th>
|
||||
<td>[ServiceAccount Deployment Service PodDisruptionBudget HorizontalPodAutoscaler]</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th>Description</th>
|
||||
<td><p>Automatically added to all resources <a href="/docs/tasks/traffic-management/ingress/gateway-api/#automated-deployment">automatically created</a> by Istio Gateway controller to indicate which <code>GatewayClass</code> resulted in the object creation. Users should not set this label themselves.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="IoK8sNetworkingGatewayGatewayName">gateway.networking.k8s.io/gateway-name</h2>
|
||||
<table class="annotations">
|
||||
<tbody>
|
||||
|
|
@ -46,7 +68,7 @@ Istio supports to control its behavior.
|
|||
</tr>
|
||||
<tr>
|
||||
<th>Resource Types</th>
|
||||
<td>[ServiceAccount Deployment Service]</td>
|
||||
<td>[ServiceAccount Deployment Service PodDisruptionBudget HorizontalPodAutoscaler]</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th>Description</th>
|
||||
|
|
|
|||
|
|
@ -574,7 +574,7 @@ gRPC Go SDK, and gRPC C++ SDK. This policy is experimental.
|
|||
WARNING: Setting compliance policy in the control plane is a necessary but
|
||||
not a sufficient requirement to achieve compliance. There are additional
|
||||
steps necessary to claim compliance, including using the validated
|
||||
cryptograhic modules (please consult
|
||||
cryptographic modules (please consult
|
||||
https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ssl#fips-140-2).</td>
|
||||
</tr>
|
||||
<tr id='dry-run-file-path'>
|
||||
|
|
|
|||
|
|
@ -8520,7 +8520,7 @@ gRPC Go SDK, and gRPC C++ SDK. This policy is experimental.
|
|||
WARNING: Setting compliance policy in the control plane is a necessary but
|
||||
not a sufficient requirement to achieve compliance. There are additional
|
||||
steps necessary to claim compliance, including using the validated
|
||||
cryptograhic modules (please consult
|
||||
cryptographic modules (please consult
|
||||
https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ssl#fips-140-2).</td>
|
||||
</tr>
|
||||
<tr id='enable-100-continue-headers'>
|
||||
|
|
|
|||
|
|
@ -795,7 +795,7 @@ gRPC Go SDK, and gRPC C++ SDK. This policy is experimental.
|
|||
WARNING: Setting compliance policy in the control plane is a necessary but
|
||||
not a sufficient requirement to achieve compliance. There are additional
|
||||
steps necessary to claim compliance, including using the validated
|
||||
cryptograhic modules (please consult
|
||||
cryptographic modules (please consult
|
||||
https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ssl#fips-140-2).</td>
|
||||
</tr>
|
||||
<tr id='credential-fetcher-type'>
|
||||
|
|
|
|||
|
|
@ -500,7 +500,7 @@ gRPC Go SDK, and gRPC C++ SDK. This policy is experimental.
|
|||
WARNING: Setting compliance policy in the control plane is a necessary but
|
||||
not a sufficient requirement to achieve compliance. There are additional
|
||||
steps necessary to claim compliance, including using the validated
|
||||
cryptograhic modules (please consult
|
||||
cryptographic modules (please consult
|
||||
https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ssl#fips-140-2).</td>
|
||||
</tr>
|
||||
<tr id='default-workload-cert-ttl'>
|
||||
|
|
|
|||
|
|
@ -33,6 +33,28 @@ Istio supports to control its behavior.
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="IoK8sNetworkingGatewayGatewayClassName">gateway.networking.k8s.io/gateway-class-name</h2>
|
||||
<table class="annotations">
|
||||
<tbody>
|
||||
<tr>
|
||||
<th>Name</th>
|
||||
<td><code>gateway.networking.k8s.io/gateway-class-name</code></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th>Feature Status</th>
|
||||
<td>Stable</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th>Resource Types</th>
|
||||
<td>[ServiceAccount Deployment Service PodDisruptionBudget HorizontalPodAutoscaler]</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th>Description</th>
|
||||
<td><p>Automatically added to all resources <a href="/zh/docs/tasks/traffic-management/ingress/gateway-api/#automated-deployment">automatically created</a> by Istio Gateway controller to indicate which <code>GatewayClass</code> resulted in the object creation. Users should not set this label themselves.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="IoK8sNetworkingGatewayGatewayName">gateway.networking.k8s.io/gateway-name</h2>
|
||||
<table class="annotations">
|
||||
<tbody>
|
||||
|
|
@ -46,7 +68,7 @@ Istio supports to control its behavior.
|
|||
</tr>
|
||||
<tr>
|
||||
<th>Resource Types</th>
|
||||
<td>[ServiceAccount Deployment Service]</td>
|
||||
<td>[ServiceAccount Deployment Service PodDisruptionBudget HorizontalPodAutoscaler]</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th>Description</th>
|
||||
|
|
|
|||
Loading…
Reference in New Issue