Clarify injection for gateways (#10998)

* Clarify injection for gateways

* Update content/en/docs/setup/install/helm/index.md

Co-authored-by: Frank Budinsky <frankb@ca.ibm.com>

Co-authored-by: Frank Budinsky <frankb@ca.ibm.com>
This commit is contained in:
John Howard 2022-03-02 12:19:05 -08:00 committed by GitHub
parent e168c8951e
commit a41e72e13d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 9 additions and 0 deletions

View File

@ -45,6 +45,10 @@ Choose the method you are most familiar with.
As a security best practice, it is recommended to deploy the gateway in a different namespace from the control plane.
{{< /tip >}}
All methods listed below rely on [Injection](/docs/setup/additional-setup/sidecar-injection/) to populate additional pod settings at runtime.
In order to support this, the namespace the gateway is deployed in must not have the `istio-injection=disabled` label.
If it does, you will see pods failing to startup attempting to pull the `auto` image, which is a placeholder that is intended to be replaced when a pod is created.
{{< tabset category-name="gateway-install-type" >}}
{{< tab name="IstioOperator" category-value="iop" >}}

View File

@ -51,6 +51,11 @@ Follow this guide to install and configure an Istio mesh using
See [Installing Gateways](/docs/setup/additional-setup/gateway/) for in-depth documentation on gateway installation.
{{< warning >}}
The namespace the gateway is deployed in must not have a `istio-injection=disabled` label.
See [Controlling the injection policy](/docs/setup/additional-setup/sidecar-injection/#controlling-the-injection-policy) for more info.
{{< /warning >}}
## Verifying the installation
Status of the installation can be verified using Helm: