mirror of https://github.com/istio/istio.io.git
Fix directory structure/heading for istioctl install (#5390)
This commit is contained in:
parent
08189f25ef
commit
db10e052ff
|
@ -89,8 +89,7 @@ The 'Authorization (RBAC)' runtime is considered Beta. However, its API is stil
|
|||
|
||||
| Feature | Phase
|
||||
|-------------------|-------------------
|
||||
| [Operator installation](/docs/setup/install/operator/) | Alpha
|
||||
| [Standalone Operator](/docs/setup/install/operator/) | Alpha
|
||||
| [Standalone Operator](/docs/ops/setup/standalone-operator/) | Alpha
|
||||
| [Kubernetes: Envoy Installation and Traffic Interception](/docs/setup/) | Stable
|
||||
| [Kubernetes: Istio Control Plane Installation](/docs/setup/) | Stable
|
||||
| [Attribute Expression Language](/docs/reference/config/policy-and-telemetry/expression-language/) | Stable
|
||||
|
|
|
@ -110,4 +110,4 @@ Istio's performance depends on your specific setup and traffic load. Because of
|
|||
|
||||
Also check out the [Istio Performance and Scalability guide]/docs/ops/performance-and-scalability) for the most up-to-date performance data for current and future releases.
|
||||
|
||||
Thank you for reading, and happy benchmarking!
|
||||
Thank you for reading, and happy benchmarking!
|
||||
|
|
|
@ -157,4 +157,4 @@ Example Istio access log (formatted in JSON):
|
|||
|
||||
{{< text json >}}
|
||||
{"level":"info","time":"2019-06-11T20:57:35.424310Z","instance":"accesslog.instance.istio-control","connection_security_policy":"mutual_tls","destinationApp":"productpage","destinationIp":"10.44.2.15","destinationName":"productpage-v1-6db7564db8-pvsnd","destinationNamespace":"default","destinationOwner":"kubernetes://apis/apps/v1/namespaces/default/deployments/productpage-v1","destinationPrincipal":"cluster.local/ns/default/sa/default","destinationServiceHost":"productpage.default.svc.cluster.local","destinationWorkload":"productpage-v1","httpAuthority":"35.202.6.119","latency":"35.076236ms","method":"GET","protocol":"http","receivedBytes":917,"referer":"","reporter":"destination","requestId":"e3f7cffb-5642-434d-ae75-233a05b06158","requestSize":0,"requestedServerName":"outbound_.9080_._.productpage.default.svc.cluster.local","responseCode":200,"responseFlags":"-","responseSize":4183,"responseTimestamp":"2019-06-11T20:57:35.459150Z","sentBytes":4328,"sourceApp":"istio-ingressgateway","sourceIp":"10.44.0.8","sourceName":"ingressgateway-7748774cbf-bvf4j","sourceNamespace":"istio-control","sourceOwner":"kubernetes://apis/apps/v1/namespaces/istio-control/deployments/ingressgateway","sourcePrincipal":"cluster.local/ns/istio-control/sa/default","sourceWorkload":"ingressgateway","url":"/productpage","userAgent":"curl/7.54.0","xForwardedFor":"10.128.0.35"}
|
||||
{{< /text >}}
|
||||
{{< /text >}}
|
||||
|
|
|
@ -21,7 +21,7 @@ For ease of the installation, they are available with a `-distroless` suffix.
|
|||
|
||||
## Install distroless images
|
||||
|
||||
Follow the [Installation Steps](/docs/setup/install/operator/) to setup Istio.
|
||||
Follow the [Installation Steps](/docs/setup/install/istioctl/) to setup Istio.
|
||||
Add the option `--set tag={{< istio_full_version >}}-distroless` to use the *distroless images*.
|
||||
|
||||
## Benefits
|
||||
|
|
|
@ -101,7 +101,7 @@ You have two ways to enable Istio to rewrite the liveness HTTP probes.
|
|||
|
||||
#### Enable globally via install option
|
||||
|
||||
[Install Istio](/docs/setup/install/operator/) with `--set values.sidecarInjectorWebhook.rewriteAppHTTPProbe=true`.
|
||||
[Install Istio](/docs/setup/install/istioctl/) with `--set values.sidecarInjectorWebhook.rewriteAppHTTPProbe=true`.
|
||||
|
||||
**Alternatively**, update the configuration map of Istio sidecar injection:
|
||||
|
||||
|
|
|
@ -8,7 +8,7 @@ force_inline_toc: true
|
|||
|
||||
{{< warning >}}
|
||||
Installing Istio with Helm has been deprecated, however, you can still use these Helm configuration options when
|
||||
[installing Istio with {{< istioctl >}}](/docs/setup/install/operator/) by prepending the string "`values.`"
|
||||
[installing Istio with {{< istioctl >}}](/docs/setup/install/istioctl/) by prepending the string "`values.`"
|
||||
to the option name. For example, instead of this `helm` command:
|
||||
|
||||
{{< text bash >}}
|
||||
|
@ -21,7 +21,7 @@ You can use this `istioctl` command:
|
|||
$ istioctl manifest generate ... --set values.global.mtls.enabled=true
|
||||
{{< /text >}}
|
||||
|
||||
Refer to [customizing the configuration](/docs/setup/install/operator/#customizing-the-configuration) for details.
|
||||
Refer to [customizing the configuration](/docs/setup/install/istioctl/#customizing-the-configuration) for details.
|
||||
{{< /warning >}}
|
||||
|
||||
{{< tip >}}
|
||||
|
|
|
@ -106,4 +106,4 @@ Duration attributes represent an amount of time, expressed as a series of decima
|
|||
* `1ms` represents 1 millisecond
|
||||
* `2.3s` represents 2.3 seconds
|
||||
* `4m` represents 4 minutes
|
||||
* `5h10m` represents 5 hours and 10 minutes
|
||||
* `5h10m` represents 5 hours and 10 minutes
|
||||
|
|
|
@ -10,4 +10,4 @@ aliases:
|
|||
- /help/glossary
|
||||
icon: glossary
|
||||
---
|
||||
∑∑
|
||||
∑∑
|
||||
|
|
|
@ -8,7 +8,7 @@ keywords: [profiles,install,helm]
|
|||
---
|
||||
|
||||
This page describes the built-in configuration profiles that can be used when
|
||||
[installing Istio](/docs/setup/install/operator/).
|
||||
[installing Istio](/docs/setup/install/istioctl/).
|
||||
The profiles provide customization of the Istio control plane and of the sidecars for the Istio data plane.
|
||||
You can start with one of Istio’s built-in configuration profiles and then further customize the configuration for
|
||||
your specific needs. The following built-in configuration profiles are currently available:
|
||||
|
@ -21,7 +21,7 @@ your specific needs. The following built-in configuration profiles are currently
|
|||
1. **demo**: configuration designed to showcase Istio functionality with modest resource requirements.
|
||||
It is suitable to run the [Bookinfo](/docs/examples/bookinfo/) application and associated tasks.
|
||||
This is the configuration that is installed with the [quick start](/docs/setup/install/kubernetes/) instructions,
|
||||
but you can later [customize the configuration](/docs/setup/install/operator/#customizing-the-configuration)
|
||||
but you can later [customize the configuration](/docs/setup/install/istioctl/#customizing-the-configuration)
|
||||
to enable additional features if you wish to explore more advanced tasks.
|
||||
|
||||
{{< warning >}}
|
||||
|
@ -59,4 +59,4 @@ The components marked as **X** are installed within each profile:
|
|||
|
||||
To further customize Istio and install addons, you can add one or more `--set <key>=<value>` options in the
|
||||
`istioctl manifest` command that you use when installing Istio.
|
||||
Refer to [customizing the configuration](/docs/setup/install/operator/#customizing-the-configuration) for details.
|
||||
Refer to [customizing the configuration](/docs/setup/install/istioctl/#customizing-the-configuration) for details.
|
||||
|
|
|
@ -21,7 +21,7 @@ window.onload = function(){
|
|||
|
||||
{{< warning >}}
|
||||
The Helm installation approach has been deprecated.
|
||||
Please use [Installing with {{< istioctl >}}](/docs/setup/install/operator/), instead.
|
||||
Please use [Installing with {{< istioctl >}}](/docs/setup/install/istioctl/), instead.
|
||||
{{< /warning >}}
|
||||
|
||||
Follow this guide to install and configure an Istio mesh for in-depth evaluation or production use.
|
||||
|
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: Installing with Istioctl
|
||||
title: Customizable Install with Istioctl
|
||||
description: Install and customize any Istio configuration profile for in-depth evaluation or production use.
|
||||
weight: 10
|
||||
keywords: [operator,kubernetes,helm]
|
||||
keywords: [istioctl,kubernetes]
|
||||
---
|
||||
|
||||
Follow this guide to install and configure an Istio mesh for in-depth evaluation or production use.
|
|
@ -18,7 +18,7 @@ access logging.
|
|||
{{< /warning >}}
|
||||
|
||||
To install Istio for production use, we recommend using the
|
||||
[Installing with {{< istioctl >}} guide](/docs/setup/install/operator/)
|
||||
[Installing with {{< istioctl >}} guide](/docs/setup/install/istioctl/)
|
||||
instead, which provides many more options for selecting and managing the Istio
|
||||
configuration. This permits customization of Istio to operator specific
|
||||
requirements.
|
||||
|
|
|
@ -31,7 +31,7 @@ Cross-cluster communication occurs over Istio gateways of the respective cluster
|
|||
|
||||
* Two or more Kubernetes clusters with versions: {{< supported_kubernetes_versions >}}.
|
||||
|
||||
* Authority to [deploy the Istio control plane](/docs/setup/install/operator/)
|
||||
* Authority to [deploy the Istio control plane](/docs/setup/install/istioctl/)
|
||||
on **each** Kubernetes cluster.
|
||||
|
||||
* The IP address of the `istio-ingressgateway` service in each cluster must be accessible
|
||||
|
@ -98,7 +98,7 @@ Cross-cluster communication occurs over Istio gateways of the respective cluster
|
|||
{{< /text >}}
|
||||
|
||||
For further details and customization options, refer to the
|
||||
[installation instructions](/docs/setup/install/operator/).
|
||||
[installation instructions](/docs/setup/install/istioctl/).
|
||||
|
||||
## Setup DNS
|
||||
|
||||
|
|
|
@ -29,7 +29,7 @@ No VPN connectivity nor direct network access between workloads in different clu
|
|||
|
||||
* Two or more Kubernetes clusters with versions: {{< supported_kubernetes_versions >}}.
|
||||
|
||||
* Authority to [deploy the Istio control plane](/docs/setup/install/operator/)
|
||||
* Authority to [deploy the Istio control plane](/docs/setup/install/istioctl/)
|
||||
|
||||
* Two Kubernetes clusters (referred to as `cluster1` and `cluster2`).
|
||||
|
||||
|
|
|
@ -26,7 +26,7 @@ Istio control plane, Envoy can then form a mesh network across multiple clusters
|
|||
|
||||
* Two or more clusters running a supported Kubernetes version ({{< supported_kubernetes_versions >}}).
|
||||
|
||||
* The ability to [deploy the Istio control plane](/docs/setup/install/operator/)
|
||||
* The ability to [deploy the Istio control plane](/docs/setup/install/istioctl/)
|
||||
on **one** of the clusters.
|
||||
|
||||
* A RFC1918 network, VPN, or an alternative more advanced network technique
|
||||
|
@ -46,7 +46,7 @@ manifests and Helm charts provided within the Istio repository.
|
|||
|
||||
## Deploy the local control plane
|
||||
|
||||
[Install the Istio control plane](/docs/setup/install/operator/)
|
||||
[Install the Istio control plane](/docs/setup/install/istioctl/)
|
||||
on **one** Kubernetes cluster.
|
||||
|
||||
## Install the Istio remote
|
||||
|
|
|
@ -23,7 +23,7 @@ Ensure you meet these requirements before starting the upgrade process:
|
|||
|
||||
* Istio version 1.3.3 or higher is installed.
|
||||
|
||||
* Your Istio installation was [installed using {{< istioctl >}}](/docs/setup/install/operator/).
|
||||
* Your Istio installation was [installed using {{< istioctl >}}](/docs/setup/install/istioctl/).
|
||||
|
||||
## Upgrade steps
|
||||
|
||||
|
@ -60,7 +60,7 @@ can be found in the `bin/` subdirectory of the downloaded package.
|
|||
{{< /text >}}
|
||||
|
||||
`<your-custom-configuration-file>` is the
|
||||
[IstioControlPlane API Custom Resource Definition](/docs/setup/install/operator/#configure-the-feature-or-component-settings)
|
||||
[IstioControlPlane API Custom Resource Definition](/docs/setup/install/istioctl/#configure-the-feature-or-component-settings)
|
||||
file you used to customize the installation of the currently-running version of Istio.
|
||||
|
||||
{{< warning >}}
|
||||
|
@ -94,7 +94,7 @@ Ensure you meet these requirements before starting the downgrade process:
|
|||
|
||||
* Istio version 1.4 or higher is installed.
|
||||
|
||||
* Your Istio installation was [installed using {{< istioctl >}}](/docs/setup/install/operator/).
|
||||
* Your Istio installation was [installed using {{< istioctl >}}](/docs/setup/install/istioctl/).
|
||||
|
||||
* Downgrade must be done using the `istioctl` binary version that
|
||||
corresponds to the Istio version that you intend to downgrade to.
|
||||
|
|
|
@ -16,7 +16,7 @@ To learn how Istio handles tracing, visit this task's [overview](../overview/).
|
|||
|
||||
## Before you begin
|
||||
|
||||
1. To set up Istio, follow the instructions in the [Installation guide](/docs/setup/install/operator)
|
||||
1. To set up Istio, follow the instructions in the [Installation guide](/docs/setup/install/istioctl)
|
||||
and then configure:
|
||||
|
||||
a) a demo/test environment by setting the `--set values.tracing.enabled=true` install option to enable tracing "out of the box"
|
||||
|
|
|
@ -95,7 +95,7 @@ percentage in one of two ways:
|
|||
|
||||
* During the mesh setup, use the option `values.pilot.traceSampling` to
|
||||
set the percentage of trace sampling. See the
|
||||
[Installing with {{< istioctl >}}](/docs/setup/install/operator/) documentation for
|
||||
[Installing with {{< istioctl >}}](/docs/setup/install/istioctl/) documentation for
|
||||
details on setting options.
|
||||
* In a running mesh, edit the `istio-pilot` deployment and
|
||||
change the environment variable with the following steps:
|
||||
|
|
|
@ -16,7 +16,7 @@ To learn how Istio handles tracing, visit this task's [overview](../overview/).
|
|||
|
||||
## Before you begin
|
||||
|
||||
1. To set up Istio, follow the instructions in the [Installation guide](/docs/setup/install/operator)
|
||||
1. To set up Istio, follow the instructions in the [Installation guide](/docs/setup/install/istioctl)
|
||||
and then configure:
|
||||
|
||||
a) a demo/test environment by setting the `--set values.tracing.enabled=true` and `--set values.tracing.provider=zipkin` install options to enable tracing "out of the box"
|
||||
|
|
|
@ -33,7 +33,7 @@ addons to require authentication when exposing them externally.
|
|||
|
||||
1. [Install cert-manager](https://docs.cert-manager.io/en/latest/getting-started/install/kubernetes.html) to manage certificates automatically.
|
||||
|
||||
1. [Install Istio](/docs/setup/install/operator) in your cluster and enable the `cert-manager` flag and configure `istio-ingressgateway` to use
|
||||
1. [Install Istio](/docs/setup/install/istioctl) in your cluster and enable the `cert-manager` flag and configure `istio-ingressgateway` to use
|
||||
the [Secret Discovery Service](https://www.envoyproxy.io/docs/envoy/latest/configuration/security/secret#sds-configuration).
|
||||
|
||||
To install Istio accordingly, use the following installation options:
|
||||
|
@ -370,7 +370,7 @@ the [Secret Discovery Service](https://www.envoyproxy.io/docs/envoy/latest/confi
|
|||
|
||||
### Option 2: Insecure access (HTTP)
|
||||
|
||||
1. [Install Istio](/docs/setup/install/operator) in your cluster with your desired telemetry addons.
|
||||
1. [Install Istio](/docs/setup/install/istioctl) in your cluster with your desired telemetry addons.
|
||||
|
||||
To additionally install the telemetry addons, use the following installation options:
|
||||
|
||||
|
@ -639,4 +639,4 @@ the [Secret Discovery Service](https://www.envoyproxy.io/docs/envoy/latest/confi
|
|||
{{< text bash >}}
|
||||
$ kubectl -n istio-system delete certificate telemetry-gw-cert
|
||||
certificate.certmanager.k8s.io "telemetry-gw-cert" deleted
|
||||
{{< /text >}}
|
||||
{{< /text >}}
|
||||
|
|
|
@ -47,7 +47,7 @@ This approach has the following benefits:
|
|||
|
||||
## Before you begin
|
||||
|
||||
* Follow the [install instructions](/docs/setup/install/operator/)
|
||||
* Follow the [install instructions](/docs/setup/install/istioctl/)
|
||||
to set up Istio with SDS and global mutual TLS enabled.
|
||||
|
||||
## Service-to-service mutual TLS using key/certificate provisioned through SDS
|
||||
|
|
|
@ -111,4 +111,4 @@ To delete the `foo` test namespace and all its resources, run:
|
|||
|
||||
{{< text bash >}}
|
||||
$ kubectl delete ns foo
|
||||
{{< /text >}}
|
||||
{{< /text >}}
|
||||
|
|
|
@ -24,7 +24,7 @@ this feature is not needed if the production setup is not using the
|
|||
|
||||
## Before you begin
|
||||
|
||||
To complete this task, you can [install Istio](/docs/setup/install/operator/) with the `global.mtls.enabled` option set to `true`.
|
||||
To complete this task, you can [install Istio](/docs/setup/install/istioctl/) with the `global.mtls.enabled` option set to `true`.
|
||||
|
||||
{{< tip >}}
|
||||
Use an [authentication policy](/docs/concepts/security/#authentication-policies) to configure mutual TLS for
|
||||
|
|
|
@ -407,7 +407,7 @@ For example, if the range is 10.0.0.1/24, use the following command:
|
|||
$ istioctl manifest apply <the flags you used to install Istio> --set values.global.proxy.includeIPRanges="10.0.0.1/24"
|
||||
{{< /text >}}
|
||||
|
||||
Use the same command that you used to [install Istio](/docs/setup/install/operator) and
|
||||
Use the same command that you used to [install Istio](/docs/setup/install/istioctl) and
|
||||
add `--set values.global.proxy.includeIPRanges="10.0.0.1/24"`.
|
||||
|
||||
### Access the external services
|
||||
|
|
|
@ -11,7 +11,7 @@ Citadel uses a flag `max-workload-cert-ttl` to control the maximum lifetime for
|
|||
workloads. The default value is 90 days. If `workload-cert-ttl` on Citadel or node agent is greater than
|
||||
`max-workload-cert-ttl`, Citadel will fail issuing the certificate.
|
||||
|
||||
You can modify a [generated manifest](/docs/setup/install/operator/#generate-a-manifest-before-installation)
|
||||
You can modify a [generated manifest](/docs/setup/install/istioctl/#generate-a-manifest-before-installation)
|
||||
file to customize the Citadel configuration.
|
||||
The following modification specifies that the Istio certificates for workloads running in Kubernetes
|
||||
has 1 hours lifetime. Besides that, the maximum allowed Istio certificate lifetime is 48 hours.
|
||||
|
|
|
@ -8,7 +8,7 @@ aliases:
|
|||
|
||||
## Installation
|
||||
|
||||
- **Added** experimental [manifest and profile commands](/docs/setup/install/operator/) to install and manage the Istio control plane for evaluation.
|
||||
- **Added** experimental [manifest and profile commands](/docs/setup/install/istioctl/) to install and manage the Istio control plane for evaluation.
|
||||
|
||||
## Traffic management
|
||||
|
||||
|
|
|
@ -89,8 +89,7 @@ The 'Authorization (RBAC)' runtime is considered Beta. However, its API is stil
|
|||
|
||||
| Feature | Phase
|
||||
|-------------------|-------------------
|
||||
| [Operator installation](/docs/setup/install/operator/) | Alpha
|
||||
| [Standalone Operator](/docs/setup/install/operator/) | Alpha
|
||||
| [Standalone Operator](/docs/ops/setup/standalone-operator/) | Alpha
|
||||
| [Kubernetes: Envoy Installation and Traffic Interception](/docs/setup/) | Stable
|
||||
| [Kubernetes: Istio Control Plane Installation](/docs/setup/) | Stable
|
||||
| [Attribute Expression Language](/docs/reference/config/policy-and-telemetry/expression-language/) | Stable
|
||||
|
|
|
@ -110,4 +110,4 @@ Istio's performance depends on your specific setup and traffic load. Because of
|
|||
|
||||
Also check out the [Istio Performance and Scalability guide]/docs/ops/performance-and-scalability) for the most up-to-date performance data for current and future releases.
|
||||
|
||||
Thank you for reading, and happy benchmarking!
|
||||
Thank you for reading, and happy benchmarking!
|
||||
|
|
|
@ -157,4 +157,4 @@ Example Istio access log (formatted in JSON):
|
|||
|
||||
{{< text json >}}
|
||||
{"level":"info","time":"2019-06-11T20:57:35.424310Z","instance":"accesslog.instance.istio-control","connection_security_policy":"mutual_tls","destinationApp":"productpage","destinationIp":"10.44.2.15","destinationName":"productpage-v1-6db7564db8-pvsnd","destinationNamespace":"default","destinationOwner":"kubernetes://apis/apps/v1/namespaces/default/deployments/productpage-v1","destinationPrincipal":"cluster.local/ns/default/sa/default","destinationServiceHost":"productpage.default.svc.cluster.local","destinationWorkload":"productpage-v1","httpAuthority":"35.202.6.119","latency":"35.076236ms","method":"GET","protocol":"http","receivedBytes":917,"referer":"","reporter":"destination","requestId":"e3f7cffb-5642-434d-ae75-233a05b06158","requestSize":0,"requestedServerName":"outbound_.9080_._.productpage.default.svc.cluster.local","responseCode":200,"responseFlags":"-","responseSize":4183,"responseTimestamp":"2019-06-11T20:57:35.459150Z","sentBytes":4328,"sourceApp":"istio-ingressgateway","sourceIp":"10.44.0.8","sourceName":"ingressgateway-7748774cbf-bvf4j","sourceNamespace":"istio-control","sourceOwner":"kubernetes://apis/apps/v1/namespaces/istio-control/deployments/ingressgateway","sourcePrincipal":"cluster.local/ns/istio-control/sa/default","sourceWorkload":"ingressgateway","url":"/productpage","userAgent":"curl/7.54.0","xForwardedFor":"10.128.0.35"}
|
||||
{{< /text >}}
|
||||
{{< /text >}}
|
||||
|
|
|
@ -21,7 +21,7 @@ For ease of the installation, they are available with a `-distroless` suffix.
|
|||
|
||||
## Install distroless images
|
||||
|
||||
Follow the [Installation Steps](/docs/setup/install/operator/) to setup Istio.
|
||||
Follow the [Installation Steps](/docs/setup/install/istioctl/) to setup Istio.
|
||||
Add the option `--set tag={{< istio_full_version >}}-distroless` to use the *distroless images*.
|
||||
|
||||
## Benefits
|
||||
|
|
|
@ -101,7 +101,7 @@ You have two ways to enable Istio to rewrite the liveness HTTP probes.
|
|||
|
||||
#### Enable globally via install option
|
||||
|
||||
[Install Istio](/docs/setup/install/operator/) with `--set values.sidecarInjectorWebhook.rewriteAppHTTPProbe=true`.
|
||||
[Install Istio](/docs/setup/install/istioctl/) with `--set values.sidecarInjectorWebhook.rewriteAppHTTPProbe=true`.
|
||||
|
||||
**Alternatively**, update the configuration map of Istio sidecar injection:
|
||||
|
||||
|
|
|
@ -106,4 +106,4 @@ Duration attributes represent an amount of time, expressed as a series of decima
|
|||
* `1ms` represents 1 millisecond
|
||||
* `2.3s` represents 2.3 seconds
|
||||
* `4m` represents 4 minutes
|
||||
* `5h10m` represents 5 hours and 10 minutes
|
||||
* `5h10m` represents 5 hours and 10 minutes
|
||||
|
|
|
@ -8,7 +8,7 @@ keywords: [profiles,install,helm]
|
|||
---
|
||||
|
||||
This page describes the built-in configuration profiles that can be used when
|
||||
[installing Istio](/docs/setup/install/operator/).
|
||||
[installing Istio](/docs/setup/install/istioctl/).
|
||||
The profiles provide customization of the Istio control plane and of the sidecars for the Istio data plane.
|
||||
You can start with one of Istio’s built-in configuration profiles and then further customize the configuration for
|
||||
your specific needs. The following built-in configuration profiles are currently available:
|
||||
|
@ -19,7 +19,7 @@ your specific needs. The following built-in configuration profiles are currently
|
|||
1. **demo**: configuration designed to showcase Istio functionality with modest resource requirements.
|
||||
It is suitable to run the [Bookinfo](/docs/examples/bookinfo/) application and associated tasks.
|
||||
This is the configuration that is installed with the [quick start](/docs/setup/install/kubernetes/) instructions,
|
||||
but you can later [customize the configuration](/docs/setup/install/operator/#customizing-the-configuration)
|
||||
but you can later [customize the configuration](/docs/setup/install/istioctl/#customizing-the-configuration)
|
||||
to enable additional features if you wish to explore more advanced tasks.
|
||||
|
||||
{{< warning >}}
|
||||
|
|
|
@ -21,7 +21,7 @@ window.onload = function(){
|
|||
|
||||
{{< warning >}}
|
||||
The Helm installation approach has been deprecated.
|
||||
Please use [Installing with {{< istioctl >}}](/docs/setup/install/operator/), instead.
|
||||
Please use [Installing with {{< istioctl >}}](/docs/setup/install/istioctl/), instead.
|
||||
{{< /warning >}}
|
||||
|
||||
Follow this guide to install and configure an Istio mesh for in-depth evaluation or production use.
|
||||
|
|
|
@ -18,7 +18,7 @@ access logging.
|
|||
{{< /warning >}}
|
||||
|
||||
To install Istio for production use, we recommend using the
|
||||
[Installing with {{< istioctl >}} guide](/docs/setup/install/operator/)
|
||||
[Installing with {{< istioctl >}} guide](/docs/setup/install/istioctl/)
|
||||
instead, which provides many more options for selecting and managing the Istio
|
||||
configuration. This permits customization of Istio to operator specific
|
||||
requirements.
|
||||
|
|
|
@ -31,7 +31,7 @@ Cross-cluster communication occurs over Istio gateways of the respective cluster
|
|||
|
||||
* Two or more Kubernetes clusters with versions: {{< supported_kubernetes_versions >}}.
|
||||
|
||||
* Authority to [deploy the Istio control plane](/docs/setup/install/operator/)
|
||||
* Authority to [deploy the Istio control plane](/docs/setup/install/istioctl/)
|
||||
on **each** Kubernetes cluster.
|
||||
|
||||
* The IP address of the `istio-ingressgateway` service in each cluster must be accessible
|
||||
|
|
|
@ -29,7 +29,7 @@ No VPN connectivity nor direct network access between workloads in different clu
|
|||
|
||||
* Two or more Kubernetes clusters with versions: {{< supported_kubernetes_versions >}}.
|
||||
|
||||
* Authority to [deploy the Istio control plane](/docs/setup/install/operator/)
|
||||
* Authority to [deploy the Istio control plane](/docs/setup/install/istioctl/)
|
||||
|
||||
* Two Kubernetes clusters (referred to as `cluster1` and `cluster2`).
|
||||
|
||||
|
|
|
@ -23,7 +23,7 @@ Ensure you meet these requirements before starting the upgrade process:
|
|||
|
||||
* Istio version 1.3.3 or higher is installed.
|
||||
|
||||
* Your Istio installation was [installed using {{< istioctl >}}](/docs/setup/install/operator/).
|
||||
* Your Istio installation was [installed using {{< istioctl >}}](/docs/setup/install/istioctl/).
|
||||
|
||||
## Upgrade steps
|
||||
|
||||
|
@ -60,7 +60,7 @@ can be found in the `bin/` subdirectory of the downloaded package.
|
|||
{{< /text >}}
|
||||
|
||||
`<your-custom-configuration-file>` is the
|
||||
[IstioControlPlane API Custom Resource Definition](/docs/setup/install/operator/#configure-the-feature-or-component-settings)
|
||||
[IstioControlPlane API Custom Resource Definition](/docs/setup/install/istioctl/#configure-the-feature-or-component-settings)
|
||||
file you used to customize the installation of the currently-running version of Istio.
|
||||
|
||||
{{< warning >}}
|
||||
|
@ -94,7 +94,7 @@ Ensure you meet these requirements before starting the downgrade process:
|
|||
|
||||
* Istio version 1.4 or higher is installed.
|
||||
|
||||
* Your Istio installation was [installed using {{< istioctl >}}](/docs/setup/install/operator/).
|
||||
* Your Istio installation was [installed using {{< istioctl >}}](/docs/setup/install/istioctl/).
|
||||
|
||||
* Downgrade must be done using the `istioctl` binary version that
|
||||
corresponds to the Istio version that you intend to downgrade to.
|
||||
|
|
|
@ -16,7 +16,7 @@ To learn how Istio handles tracing, visit this task's [overview](../overview/).
|
|||
|
||||
## Before you begin
|
||||
|
||||
1. To set up Istio, follow the instructions in the [Installation guide](/docs/setup/install/operator)
|
||||
1. To set up Istio, follow the instructions in the [Installation guide](/docs/setup/install/istioctl)
|
||||
and then configure:
|
||||
|
||||
a) a demo/test environment by setting the `--set values.tracing.enabled=true` install option to enable tracing "out of the box"
|
||||
|
|
|
@ -95,7 +95,7 @@ percentage in one of two ways:
|
|||
|
||||
* During the mesh setup, use the option `values.pilot.traceSampling` to
|
||||
set the percentage of trace sampling. See the
|
||||
[Installing with {{< istioctl >}}](/docs/setup/install/operator/) documentation for
|
||||
[Installing with {{< istioctl >}}](/docs/setup/install/istioctl/) documentation for
|
||||
details on setting options.
|
||||
* In a running mesh, edit the `istio-pilot` deployment and
|
||||
change the environment variable with the following steps:
|
||||
|
|
|
@ -16,7 +16,7 @@ To learn how Istio handles tracing, visit this task's [overview](../overview/).
|
|||
|
||||
## Before you begin
|
||||
|
||||
1. To set up Istio, follow the instructions in the [Installation guide](/docs/setup/install/operator)
|
||||
1. To set up Istio, follow the instructions in the [Installation guide](/docs/setup/install/istioctl)
|
||||
and then configure:
|
||||
|
||||
a) a demo/test environment by setting the `--set values.tracing.enabled=true` and `--set values.tracing.provider=zipkin` install options to enable tracing "out of the box"
|
||||
|
|
|
@ -33,7 +33,7 @@ addons to require authentication when exposing them externally.
|
|||
|
||||
1. [Install cert-manager](https://docs.cert-manager.io/en/latest/getting-started/install/kubernetes.html) to manage certificates automatically.
|
||||
|
||||
1. [Install Istio](/docs/setup/install/operator) in your cluster and enable the `cert-manager` flag and configure `istio-ingressgateway` to use
|
||||
1. [Install Istio](/docs/setup/install/istioctl) in your cluster and enable the `cert-manager` flag and configure `istio-ingressgateway` to use
|
||||
the [Secret Discovery Service](https://www.envoyproxy.io/docs/envoy/latest/configuration/security/secret#sds-configuration).
|
||||
|
||||
To install Istio accordingly, use the following installation options:
|
||||
|
@ -370,7 +370,7 @@ the [Secret Discovery Service](https://www.envoyproxy.io/docs/envoy/latest/confi
|
|||
|
||||
### Option 2: Insecure access (HTTP)
|
||||
|
||||
1. [Install Istio](/docs/setup/install/operator) in your cluster with your desired telemetry addons.
|
||||
1. [Install Istio](/docs/setup/install/istioctl) in your cluster with your desired telemetry addons.
|
||||
|
||||
To additionally install the telemetry addons, use the following installation options:
|
||||
|
||||
|
@ -639,4 +639,4 @@ the [Secret Discovery Service](https://www.envoyproxy.io/docs/envoy/latest/confi
|
|||
{{< text bash >}}
|
||||
$ kubectl -n istio-system delete certificate telemetry-gw-cert
|
||||
certificate.certmanager.k8s.io "telemetry-gw-cert" deleted
|
||||
{{< /text >}}
|
||||
{{< /text >}}
|
||||
|
|
|
@ -47,7 +47,7 @@ This approach has the following benefits:
|
|||
|
||||
## Before you begin
|
||||
|
||||
* Follow the [install instructions](/docs/setup/install/operator/)
|
||||
* Follow the [install instructions](/docs/setup/install/istioctl/)
|
||||
to set up Istio with SDS and global mutual TLS enabled.
|
||||
|
||||
## Service-to-service mutual TLS using key/certificate provisioned through SDS
|
||||
|
|
|
@ -111,4 +111,4 @@ To delete the `foo` test namespace and all its resources, run:
|
|||
|
||||
{{< text bash >}}
|
||||
$ kubectl delete ns foo
|
||||
{{< /text >}}
|
||||
{{< /text >}}
|
||||
|
|
|
@ -24,7 +24,7 @@ this feature is not needed if the production setup is not using the
|
|||
|
||||
## Before you begin
|
||||
|
||||
To complete this task, you can [install Istio](/docs/setup/install/operator/) with the `global.mtls.enabled` option set to `true`.
|
||||
To complete this task, you can [install Istio](/docs/setup/install/istioctl/) with the `global.mtls.enabled` option set to `true`.
|
||||
|
||||
{{< tip >}}
|
||||
Use an [authentication policy](/docs/concepts/security/#authentication-policies) to configure mutual TLS for
|
||||
|
|
|
@ -407,7 +407,7 @@ For example, if the range is 10.0.0.1/24, use the following command:
|
|||
$ istioctl manifest apply <the flags you used to install Istio> --set values.global.proxy.includeIPRanges="10.0.0.1/24"
|
||||
{{< /text >}}
|
||||
|
||||
Use the same command that you used to [install Istio](/docs/setup/install/operator) and
|
||||
Use the same command that you used to [install Istio](/docs/setup/install/istioctl) and
|
||||
add `--set values.global.proxy.includeIPRanges="10.0.0.1/24"`.
|
||||
|
||||
### Access the external services
|
||||
|
|
|
@ -8,7 +8,7 @@ aliases:
|
|||
|
||||
## Installation
|
||||
|
||||
- **Added** experimental [manifest and profile commands](/docs/setup/install/operator/) to install and manage the Istio control plane for evaluation.
|
||||
- **Added** experimental [manifest and profile commands](/docs/setup/install/istioctl/) to install and manage the Istio control plane for evaluation.
|
||||
|
||||
## Traffic management
|
||||
|
||||
|
|
Loading…
Reference in New Issue