mirror of https://github.com/istio/istio.io.git
Change all references to istio-demo-*.yaml (#1696)
Remove demo from all documentation references
This commit is contained in:
Steven Dake
Martin Taillefer
parent
63cfc64693
commit
4ebbb12505
|
|
@ -260,7 +260,7 @@ Install Istio's core components. Choose one of the four _**mutually exclusive**_
|
|||
* Install Istio without enabling [mutual TLS authentication](/docs/concepts/security/mutual-tls/) between sidecars. Choose this option for clusters with existing applications, applications where services with an Istio sidecar need to be able to communicate with other non-Istio Kubernetes services, and applications that use [liveness and readiness probes](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/), headless services, or StatefulSets.
|
||||
|
||||
{{< text bash >}}
|
||||
$ kubectl apply -f install/kubernetes/istio-demo.yaml
|
||||
$ kubectl apply -f install/kubernetes/istio.yaml
|
||||
{{< /text >}}
|
||||
|
||||
OR
|
||||
|
|
@ -268,7 +268,7 @@ OR
|
|||
* Install Istio and enforce mutual TLS authentication between sidecars by default. Use this option only on a fresh kubernetes cluster where newly deployed workloads are guaranteed to have Istio sidecars installed.
|
||||
|
||||
{{< text bash >}}
|
||||
$ kubectl apply -f install/kubernetes/istio-demo-auth.yaml
|
||||
$ kubectl apply -f install/kubernetes/istio-auth.yaml
|
||||
{{< /text >}}
|
||||
|
||||
OR
|
||||
|
|
@ -357,10 +357,10 @@ $ istioctl kube-inject -f <your-app-spec>.yaml | kubectl apply -f -
|
|||
deletes the RBAC permissions, the `istio-system` namespace, and hierarchically all resources under it.
|
||||
It is safe to ignore errors for non-existent resources because they may have been deleted hierarchically.
|
||||
|
||||
If you installed Istio with `istio-demo.yaml`:
|
||||
If you installed Istio with `istio.yaml`:
|
||||
|
||||
{{< text bash >}}
|
||||
$ kubectl delete -f install/kubernetes/istio-demo.yaml
|
||||
$ kubectl delete -f install/kubernetes/istio.yaml
|
||||
{{< /text >}}
|
||||
|
||||
otherwise [uninstall Istio with Helm](/docs/setup/kubernetes/helm-install/#uninstall).
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ Through this task, you will learn how to:
|
|||
|
||||
* Understand Istio [authentication policy](/docs/concepts/security/authn-policy/) and related [mutual TLS authentication](/docs/concepts/security/mutual-tls/) concepts.
|
||||
|
||||
* Have a Kubernetes cluster with Istio installed, without global mutual TLS enabled (e.g use `install/kubernetes/istio-demo.yaml` as described in [installation steps](/docs/setup/kubernetes/quick-start/#installation-steps), or set `global.mtls.enabled` to false using [Helm](/docs/setup/kubernetes/helm-install/)).
|
||||
* Have a Kubernetes cluster with Istio installed, without global mutual TLS enabled (e.g use `install/kubernetes/istio.yaml` as described in [installation steps](/docs/setup/kubernetes/quick-start/#installation-steps), or set `global.mtls.enabled` to false using [Helm](/docs/setup/kubernetes/helm-install/)).
|
||||
|
||||
* For demo, create two namespaces `foo` and `bar`, and deploy [httpbin]({{< github_tree >}}/samples/httpbin) and [sleep]({{< github_tree >}}/samples/sleep) with sidecar on both of them. Also, run another httpbin and sleep app without sidecar (to keep it separate, run them in `legacy` namespace). In a regular system, a service can be both *server* (receiving traffic) for some services, and *client* for some others. For simplicity, in this demo, we only use `sleep` apps as clients, and `httpbin` as servers.
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ this feature is not needed if the production setup is not using the
|
|||
[quick start](/docs/setup/kubernetes/quick-start/) with global mutual TLS enabled:
|
||||
|
||||
{{< text bash >}}
|
||||
$ kubectl apply -f install/kubernetes/istio-demo-auth.yaml
|
||||
$ kubectl apply -f install/kubernetes/istio-auth.yaml
|
||||
{{< /text >}}
|
||||
|
||||
_**OR**_
|
||||
|
|
|
|||
|
|
@ -142,7 +142,7 @@ You need to deploy Istio control plane with mutual TLS enabled. If you have isti
|
|||
control plane with mutual TLS disabled installed, please delete it:
|
||||
|
||||
{{< text bash >}}
|
||||
$ kubectl delete -f install/kubernetes/istio-demo.yaml
|
||||
$ kubectl delete -f install/kubernetes/istio.yaml
|
||||
{{< /text >}}
|
||||
|
||||
And wait for everything is down, i.e., there is no pod in control plane namespace (istio-system).
|
||||
|
|
@ -155,7 +155,7 @@ No resources found.
|
|||
Then deploy the Istio control plane with mutual TLS enabled:
|
||||
|
||||
{{< text bash >}}
|
||||
$ kubectl apply -f install/kubernetes/istio-demo-auth.yaml
|
||||
$ kubectl apply -f install/kubernetes/istio-auth.yaml
|
||||
{{< /text >}}
|
||||
|
||||
Make sure everything is up and running:
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@ Citadel is up if the "AVAILABLE" column is 1.
|
|||
|
||||
### Verifying service configuration
|
||||
|
||||
* Check installation mode. If mutual TLS is enabled by default (e.g `istio-demo-auth.yaml` was used when installing Istio), you can expect to see uncommented `authPolicy: MUTUAL_TLS` in the configmap.
|
||||
* Check installation mode. If mutual TLS is enabled by default (e.g `istio-auth.yaml` was used when installing Istio), you can expect to see uncommented `authPolicy: MUTUAL_TLS` in the configmap.
|
||||
|
||||
{{< text bash >}}
|
||||
$ kubectl get configmap istio -o yaml -n istio-system | grep authPolicy | head -1
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ operator-specified root certificate. This task demonstrates an example to plug c
|
|||
[quick start](/docs/setup/kubernetes/quick-start/) with global mutual TLS enabled:
|
||||
|
||||
{{< text bash >}}
|
||||
$ kubectl apply -f install/kubernetes/istio-demo-auth.yaml
|
||||
$ kubectl apply -f install/kubernetes/istio-auth.yaml
|
||||
{{< /text >}}
|
||||
|
||||
_**OR**_
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ example application for this task.
|
|||
|
||||
* Setup Istio by following the instructions in the [Installation guide](/docs/setup/).
|
||||
|
||||
Either use the `istio-demo.yaml` (or `istio-demo-auth.yaml`) template, which includes tracing support, or
|
||||
Either use the `istio.yaml` (or `istio-auth.yaml`) template, which includes tracing support, or
|
||||
use the helm chart with tracing enabled using the `--set tracing.enabled=true` option.
|
||||
|
||||
* Deploy the [Bookinfo](/docs/examples/bookinfo/) sample application.
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ application.
|
|||
## Querying Istio Metrics
|
||||
|
||||
1. Verify that the prometheus service is running in your cluster (since 0.8 the
|
||||
prometheus setup is included in istio-demo.yaml and istio-demo-auth.yaml by default)
|
||||
prometheus setup is included in istio.yaml and istio-auth.yaml by default)
|
||||
|
||||
In Kubernetes environments, execute the following command:
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ There are three options for liveness and readiness probes in Kubernetes: 1) comm
|
|||
|
||||
* Understand [Kubernetes liveness and readiness probes](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/), Istio [authentication policy](/docs/concepts/security/authn-policy/) and [mutual TLS authentication](/docs/concepts/security/mutual-tls/) concepts.
|
||||
|
||||
* Have a Kubernetes cluster with Istio installed, without global mutual TLS enabled (e.g use istio-demo.yaml as described in [installation steps](/docs/setup/kubernetes/quick-start/#installation-steps), or set `global.mtls.enabled` to false using [Helm](/docs/setup/kubernetes/helm-install/)).
|
||||
* Have a Kubernetes cluster with Istio installed, without global mutual TLS enabled (e.g use istio.yaml as described in [installation steps](/docs/setup/kubernetes/quick-start/#installation-steps), or set `global.mtls.enabled` to false using [Helm](/docs/setup/kubernetes/helm-install/)).
|
||||
|
||||
## Liveness and readiness probes with command option
|
||||
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ keywords: [tenancy]
|
|||
|
||||
### 多个 Istio 控制面
|
||||
|
||||
要部署多个 Istio 控制面，首先要在 Istio 清单文件中对所有的 `namespace` 引用进行替换。以 `istio.yaml` （0.8 中应该是 `istio-demo.yaml`） 为例：如果需要两个租户级的 Istio 控制面，那么第一个租户可以使用 `istio.yaml` 中的缺省命名空间也就是 `istio-system`；而第二个租户就要生成一个新的 Yaml 文件，并在其中使用不同的命名空间。例如使用下面的命令创建一个使用 `istio-system1` 命名空间的 Yaml 文件：
|
||||
要部署多个 Istio 控制面，首先要在 Istio 清单文件中对所有的 `namespace` 引用进行替换。以 `istio.yaml` （0.8 中应该是 `istio.yaml`） 为例：如果需要两个租户级的 Istio 控制面，那么第一个租户可以使用 `istio.yaml` 中的缺省命名空间也就是 `istio-system`；而第二个租户就要生成一个新的 Yaml 文件，并在其中使用不同的命名空间。例如使用下面的命令创建一个使用 `istio-system1` 命名空间的 Yaml 文件：
|
||||
|
||||
{{< text bash >}}
|
||||
$ cat istio.yaml | sed s/istio-system/istio-system1/g > istio-system1.yaml
|
||||
|
|
|
|||
|
|
@ -255,7 +255,7 @@ $ kubectl describe pod --namespace kube-system $(kubectl get pods --namespace ku
|
|||
* 安装 Istio 而不启用 sidecar 之间的[双向TLS验证](/docs/concepts/security/mutual-tls/)。对于现有应用程序的集群，使用 Istio sidecar 的服务需要能够与其他非 Istio Kubernetes 服务以及使用[存活和就绪探针](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/)、headless 服务或 StatefulSets 的应用程序通信的应用程序选择此选项。
|
||||
|
||||
{{< text bash >}}
|
||||
$ kubectl apply -f install/kubernetes/istio-demo.yaml
|
||||
$ kubectl apply -f install/kubernetes/istio.yaml
|
||||
{{< /text >}}
|
||||
|
||||
或者
|
||||
|
|
@ -263,7 +263,7 @@ $ kubectl apply -f install/kubernetes/istio-demo.yaml
|
|||
* 默认情况下安装 Istio，并强制在 sidecar 之间进行双向 TLS 身份验证。仅在保证新部署的工作负载安装了 Istio sidecar 的新建的 kubernetes 集群上使用此选项。
|
||||
|
||||
{{< text bash >}}
|
||||
$ kubectl apply -f install/kubernetes/istio-demo-auth.yaml
|
||||
$ kubectl apply -f install/kubernetes/istio-auth.yaml
|
||||
{{< /text >}}
|
||||
|
||||
或者
|
||||
|
|
@ -332,10 +332,10 @@ $ kubectl create -f <(istioctl kube-inject -f <your-app-spec>.yaml)
|
|||
|
||||
不必理会在层级删除过程中的各种报错，因为这些资源可能已经被删除的。
|
||||
|
||||
如果您使用 `istio-demo.yaml` 安装的 Istio：
|
||||
如果您使用 `istio.yaml` 安装的 Istio：
|
||||
|
||||
{{< text bash >}}
|
||||
$ kubectl delete -f install/kubernetes/istio-demo.yaml
|
||||
$ kubectl delete -f install/kubernetes/istio.yaml
|
||||
{{< /text >}}
|
||||
|
||||
否则使用 [Helm 卸载 Istio](/docs/setup/kubernetes/helm-install/#uninstall)。
|
||||
|
|
|
|||
Loading…
Reference in New Issue