mirror of https://github.com/istio/istio.io.git
Move FAQ to be a top level section. (#4104)
Signed-off-by: rcaballeromx <grca@google.com>
This commit is contained in:
Rigs Caballero
Martin Taillefer
parent
bf4901af38
commit
e2be3ddf16
|
|
@ -657,12 +657,12 @@ title: Frequently Asked Questions
|
|||
description: Questions Asked Frequently.
|
||||
weight: 12
|
||||
aliases:
|
||||
- /faq
|
||||
- /help/faq
|
||||
---
|
||||
{{< /text >}}
|
||||
|
||||
With the above in a page saved as `help/faq.md`, the user will be able to access the page by going
|
||||
to `istio.io/help/faq/` as normal, as well as `istio.io/faq/`.
|
||||
With the above in a page saved as `faq/_index.md`, the user will be able to access the page by going
|
||||
to `istio.io/faq/` as normal, as well as `istio.io/help/faq/`.
|
||||
|
||||
You can also add many redirects like so:
|
||||
|
||||
|
|
|
|||
|
|
@ -97,7 +97,7 @@ Below is our list of existing features and their current phases. This informatio
|
|||
| [Kubernetes: Istio Control Plane Upgrade](/docs/setup/kubernetes/) | Beta
|
||||
| [Consul Integration](/docs/setup/consul/quick-start/) | Alpha
|
||||
| Basic Configuration Resource Validation | Alpha
|
||||
| [Mixer Self Monitoring](/help/faq/mixer/#mixer-self-monitoring) | Beta
|
||||
| [Mixer Self Monitoring](/faq/mixer/#mixer-self-monitoring) | Beta
|
||||
| [Custom Mixer Build Model](https://github.com/istio/istio/wiki/Mixer-Compiled-In-Adapter-Dev-Guide) | deprecated
|
||||
| [Out of Process Mixer Adapters (gRPC Adapters)](https://github.com/istio/istio/wiki/Mixer-Out-Of-Process-Adapter-Dev-Guide) | Beta
|
||||
| [Istio CNI plugin](/docs/setup/kubernetes/additional-setup/cni/) | Alpha
|
||||
|
|
|
|||
|
|
@ -86,7 +86,7 @@ concise list of things you should know before upgrading your deployment to Istio
|
|||
## Security
|
||||
|
||||
- **Readiness and Liveness Probes**. Added support for Kubernetes' HTTP
|
||||
[readiness and liveness probes](/help/faq/security/#k8s-health-checks) when
|
||||
[readiness and liveness probes](/faq/security/#k8s-health-checks) when
|
||||
mutual TLS is enabled.
|
||||
|
||||
- **Cluster RBAC Configuration**. Replaced the `RbacConfig` resource with the
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ icon: docs
|
|||
|
||||
In addition to the documentation, we provide the following resources:
|
||||
|
||||
- [FAQ](/help/faq) section
|
||||
- [FAQ](/faq) section
|
||||
- [Glossary](/docs/reference/glossary).
|
||||
- [Release notes](/about/notes) for info on individual Istio releases.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,12 +1,13 @@
|
|||
---
|
||||
title: FAQ
|
||||
description: Frequently Asked Questions about Istio.
|
||||
weight: 20
|
||||
weight: 1
|
||||
layout: faq-landing
|
||||
aliases:
|
||||
- /faq
|
||||
- /docs/welcome/faq.html
|
||||
- /docs/reference/faq.html
|
||||
- /help/faq/
|
||||
icon: faq
|
||||
---
|
||||
|
||||
|
|
@ -6,4 +6,4 @@ weight: 20
|
|||
Although an Istio sidecar will process both inbound and outbound requests for an associated application instance, it has no implicit way of correlating
|
||||
the outbound requests to the inbound request that caused them. The only way this correlation can be achieved is if the application
|
||||
propagates relevant information (i.e. headers) from the inbound request to the outbound requests. Header propagation may be accomplished through client
|
||||
libraries or manually. Further discussion is provided in [What is required for distributed tracing with Istio?](/help/faq/distributed-tracing/#how-to-support-tracing).
|
||||
libraries or manually. Further discussion is provided in [What is required for distributed tracing with Istio?](/faq/distributed-tracing/#how-to-support-tracing).
|
||||
|
|
@ -7,5 +7,5 @@ Since Istio 1.0.3, the default sampling rate for tracing has been reduced to 1%
|
|||
instances captured by Istio will be reported to the tracing backend. The sampling rate in the `istio-demo.yaml` is still set to 100%. See
|
||||
[this section](/docs/tasks/telemetry/distributed-tracing/overview/#trace-sampling) for more information on how to set the sampling rate.
|
||||
|
||||
If you still do not see any trace data, please confirm that your ports conform to the Istio [port naming conventions](/help/faq/traffic-management/#naming-port-convention) and that the appropriate container port is exposed (via pod spec, for example) to enable
|
||||
traffic capture by the sidecar proxy (Envoy).
|
||||
If you still do not see any trace data, please confirm that your ports conform to the Istio [port naming conventions](/faq/traffic-management/#naming-port-convention) and that the appropriate container port is exposed (via pod spec, for example) to enable
|
||||
traffic capture by the sidecar proxy (Envoy).
|
||||
|
|
@ -1,11 +0,0 @@
|
|||
---
|
||||
title: Need Help?
|
||||
linktitle: Help
|
||||
description: A bunch of resources to help you deploy, configure and use Istio.
|
||||
weight: 10
|
||||
sidebar_singlecard: true
|
||||
icon: help
|
||||
---
|
||||
|
||||
And don't forget our vibrant [community](/about/community/) that's always ready to lend a hand
|
||||
with thorny problems.
|
||||
|
|
@ -78,7 +78,7 @@ icon: feature-status
|
|||
| [Kubernetes：Istio 控制平面升级](/zh/docs/setup/kubernetes/) | Beta
|
||||
| [Consul 集成](/zh/docs/setup/consul/quick-start/) | Alpha
|
||||
| 基本配置资源校验 | Alpha
|
||||
| [Mixer 遥测收集（追踪、日志记录、监控）](/help/faq/mixer/#mixer-self-monitoring) | Alpha
|
||||
| [Mixer 遥测收集（追踪、日志记录、监控）](/faq/mixer/#mixer-self-monitoring) | Alpha
|
||||
| [自定义 Mixer 构建模型](https://github.com/istio/istio/wiki/Mixer-Compiled-In-Adapter-Dev-Guide) | Alpha
|
||||
| [进程外 Mixer 适配器（ gRPC Adapters ）](https://github.com/istio/istio/wiki/Mixer-Out-Of-Process-Adapter-Dev-Guide) | Alpha
|
||||
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@
|
|||
|
||||
## 安全性
|
||||
|
||||
- **存活及就绪检测**：在启用双向 TLS 的情况下，增加 Kubernetes 的 HTTP [存活及就需检测](/zh/help/faq/security/#k8s-health-checks)支持。
|
||||
- **存活及就绪检测**：在启用双向 TLS 的情况下，增加 Kubernetes 的 HTTP [存活及就需检测](/zh/faq/security/#k8s-health-checks)支持。
|
||||
|
||||
- **集群级的 RBAC 配置**：用 `ClusterRbacConfig` 代替 `RbacConfig`，用于配置集群级别的生效范围。具体升级步骤可以参看[从 `RbacConfig` 迁移到 `ClusterRbacConfig`](/docs/setup/kubernetes/upgrade/steps/#migrating-from-rbacconfig-to-clusterrbacconfig)。
|
||||
|
||||
|
|
@ -125,4 +125,4 @@
|
|||
|
||||
- **过期命令**：`istioctl create`、`istioctl replace`、`istioctl get` 和 `istioctl delete` 命令都已过期，改用 [`kubectl`](https://kubernetes.io/docs/tasks/tools/install-kubectl) 命令执行相关任务。`istioctl gen-deploy` 命令也同样过期，使用 [`helm template`](/zh/docs/setup/kubernetes/install/helm/#方案-1-使用-helm-template-进行安装) 命令来替代。1.12 版本中会移除这些命令。
|
||||
|
||||
- **短命令**：在 `kubectl` 中包含了 `Gateway`、`VirtualService`、`DestinationRules` 以及 `ServiceEntry` 的短命令。
|
||||
- **短命令**：在 `kubectl` 中包含了 `Gateway`、`VirtualService`、`DestinationRules` 以及 `ServiceEntry` 的短命令。
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ icon: docs
|
|||
|
||||
另外，您可能会发现这些有趣的链接：
|
||||
|
||||
- 查看我们的[帮助](/zh/help)文档，其中包括我们的[操作指南](/zh/docs/ops)、[FAQ](/zh/help/faq)和[词汇表](/zh/docs/reference/glossary)。
|
||||
- 查看我们的[帮助](/zh/docs)文档，其中包括我们的[操作指南](/zh/docs/ops)、[FAQ](/zh/faq)和[词汇表](/zh/docs/reference/glossary)。
|
||||
|
||||
- 有关各个 Istio 版本的信息，请参阅[发行说明](/zh/about/notes)。
|
||||
|
||||
|
|
|
|||
|
|
@ -6,4 +6,4 @@ weight: 20
|
|||
尽管 Istio sidecar 将处理与之关联的应用程序实例的入站和出站请求，但它并不能隐式地将出站请求和与该出站请求对应的入站请求建立联系。
|
||||
实现这种相关性的唯一方法是应用程序[传递从入站请求到出站请求的关联信息](/zh/docs/tasks/telemetry/distributed-tracing/overview/#understanding-what-happened)（比如，header）。
|
||||
header 的传播可以通过客户端库或手动完成。
|
||||
[使用 Istio 进行分布式追踪需要什么？](/zh/help/faq/distributed-tracing/#how-to-support-tracing)提供了进一步的讨论。
|
||||
[使用 Istio 进行分布式追踪需要什么？](/zh/faq/distributed-tracing/#how-to-support-tracing)提供了进一步的讨论。
|
||||
|
|
@ -8,5 +8,5 @@ weight: 30
|
|||
`istio-demo.yaml` 文件中的采样率仍设为 100%。
|
||||
有关如何设置采样率的更多信息，可参见[本节](/zh/docs/tasks/telemetry/distributed-tracing/overview/#trace-sampling)。
|
||||
|
||||
如果您仍然没有看到任何追踪数据，请确认您的端口符合 Istio [端口命名规范](/zh/help/faq/traffic-management/#naming-port-convention)，
|
||||
如果您仍然没有看到任何追踪数据，请确认您的端口符合 Istio [端口命名规范](/zh/faq/traffic-management/#naming-port-convention)，
|
||||
并公开适当的容器端口（例如，通过 pod spec）来使得 sidecar 代理（Envoy）能够对流量进行捕获。
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue