Automated merge

* upstream/main:
  Remove the redundant step while creating the Istio resource. (openshift-service-mesh#149)
  Add gateway instructions to user docs (openshift-service-mesh#146)

bundle/README.md

@@ -60,11 +60,10 @@ Repeat the process to create a project named `istio-cni`.
 ### Creating the Istio resource
 
 1. In the OpenShift Container Platform web console, click **Operators** -> **Installed Operators**. 
-1. Select `istio-system` in the **Project** drop-down menu.
+1. Select the `istio-system` project from the **Namespace** drop-down menu.
 1. Click the sail-operator.
 1. Click **Istio**.
 1. Click **Create Istio**.
-1. Select the `istio-system` project from the **Namespace** drop-down menu.
 1. Click **Create**. This action deploys the Istio control plane.
 1. When `State: Healthy` appears in the `Status` column, Istio is successfully deployed.
 

docs/README.md

@@ -10,7 +10,10 @@ tbd
 tbd
 
 ## Gateways
-tbd
+
+The Sail-operator does not manage Gateways. You can deploy a gateway manually either through [gateway-api](https://istio.io/latest/docs/tasks/traffic-management/ingress/gateway-api/) or through [gateway injection](https://istio.io/latest/docs/setup/additional-setup/gateway/#deploying-a-gateway). As you are following the gateway installation instructions, skip the step to install Istio since this is handled by the Sail-operator.
+
+**Note:** The `IstioOperator` / `istioctl` example is separate from the Sail-operator. Setting `spec.components` or `spec.values.gateways` on your Sail-operator `Istio` resource **will not work**.
 
 ## Multicluster
 tbd