Require Gateway API in 2.19 docs

linkerd.io/content/2-edge/features/gateway-api.md

@@ -12,8 +12,7 @@ versions of Linkerd fully support the
 configuration mechanism, and many Linkerd features, including [authorization
 policies][auth-policy], [dynamic traffic routing][dyn-routing], and [request
 timeouts][timeouts], require these resource types from the Gateway API in order
-to be used. (Note that Linkerd does not require these types in order to run, but
-these features will not be useable.)
+to be used.
 
 The two primary Gateway API types used to configure Linkerd are:
 

linkerd.io/content/2-edge/getting-started/_index.md

@@ -87,17 +87,15 @@ worry—we'll fix that soon enough.
 Make sure that your Linkerd version and Kubernetes version are compatible by
 checking Linkerd's [supported Kubernetes versions](../reference/k8s-versions/).
 
-## Step 2 (optional): Install the Gateway API
+## Step 2: Install the Gateway API
 
 Several features in Linkerd are configured using CRDs from the
 [Gateway API](https://gateway-api.sigs.k8s.io/) project, including authorization
 policy and dynamic request routing. In many Kubernetes clusters, these CRDs are
-already available, but if they aren't, you won't be able to use those features
-unless you install these CRDs.
+already available, but if they aren't, you will need to install it first.
 
-If you want to use those features, follow our
-[Gateway API Linkerd doc](../features/gateway-api/) to ensure the Gateway API
-CRDs are installed. You can always do this step later.
+Follow [these instructions](../features/gateway-api/) for determining if the
+Gateway API is installed or how to install it.
 
 ## Step 3: Validate your Kubernetes cluster
 

linkerd.io/content/2-edge/tasks/install-helm.md

@@ -8,6 +8,16 @@ command. This is recommended for production, since it allows for repeatability.
 
 {{< docs/edge-note >}}
 
+## Prerequisite: install the Gateway API
+
+Several features in Linkerd are configured using CRDs from the
+[Gateway API](https://gateway-api.sigs.k8s.io/) project, including authorization
+policy and dynamic request routing. In many Kubernetes clusters, these CRDs are
+already available, but if they aren't, you will need to install it first.
+
+Follow [these instructions](../features/gateway-api/) for determining if the
+Gateway API is installed or how to install it.
+
 ## Prerequisite: generate mTLS certificates
 
 To do [automatic mutual TLS](../features/automatic-mtls/), Linkerd requires
@@ -40,15 +50,11 @@ intended. Instrunctions are on the
 
 ### linkerd-crds
 
-The `linkerd-crds` chart sets up the CRDs linkerd requires. If the Gateway API
-has already been installed on the cluster, you must specify
-`--set installGatewayAPI=false` or add this to the `values.yml` in order to
-avoid a conflict. See [the Gateway API](../features/gateway-api/) for more
-details.
+The `linkerd-crds` chart sets up the CRDs linkerd requires:
 
 ```bash
 helm install linkerd-crds linkerd-edge/linkerd-crds \
-  -n linkerd --create-namespace --set installGatewayAPI=false
+  -n linkerd --create-namespace
 ```
 
 {{< note >}}

linkerd.io/content/2-edge/tasks/install.md

@@ -37,6 +37,13 @@ local machine, or even somewhere else.
 Make sure that your Linkerd version and Kubernetes version are compatible by
 checking Linkerd's [supported Kubernetes versions](../reference/k8s-versions/).
 
+Linkerd also requires the [Gateway API](https://gateway-api.sigs.k8s.io/) CRDs.
+In many Kubernetes clusters, these CRDs are already available, but if they
+aren't, you will need to install it first.
+
+Follow [these instructions](../features/gateway-api/) for determining if the
+Gateway API is installed or how to install it.
+
 Before installing the control plane, validate that this Kubernetes cluster is
 configured appropriately for Linkerd by running:
 

linkerd.io/content/2.19/features/gateway-api.md

@@ -12,8 +12,7 @@ versions of Linkerd fully support the
 configuration mechanism, and many Linkerd features, including [authorization
 policies][auth-policy], [dynamic traffic routing][dyn-routing], and [request
 timeouts][timeouts], require these resource types from the Gateway API in order
-to be used. (Note that Linkerd does not require these types in order to run, but
-these features will not be useable.)
+to be used.
 
 The two primary Gateway API types used to configure Linkerd are:
 

linkerd.io/content/2.19/getting-started/_index.md

@@ -87,17 +87,15 @@ worry—we'll fix that soon enough.
 Make sure that your Linkerd version and Kubernetes version are compatible by
 checking Linkerd's [supported Kubernetes versions](../reference/k8s-versions/).
 
-## Step 2 (optional): Install the Gateway API
+## Step 2: Install the Gateway API
 
 Several features in Linkerd are configured using CRDs from the
 [Gateway API](https://gateway-api.sigs.k8s.io/) project, including authorization
 policy and dynamic request routing. In many Kubernetes clusters, these CRDs are
-already available, but if they aren't, you won't be able to use those features
-unless you install these CRDs.
+already available, but if they aren't, you will need to install it first.
 
-If you want to use those features, follow our
-[Gateway API Linkerd doc](../features/gateway-api/) to ensure the Gateway API
-CRDs are installed. You can always do this step later.
+Follow [these instructions](../features/gateway-api/) for determining if the
+Gateway API is installed or how to install it.
 
 ## Step 3: Validate your Kubernetes cluster
 

linkerd.io/content/2.19/tasks/install-helm.md

@@ -8,6 +8,16 @@ command. This is recommended for production, since it allows for repeatability.
 
 {{< docs/edge-note >}}
 
+## Prerequisite: install the Gateway API
+
+Several features in Linkerd are configured using CRDs from the
+[Gateway API](https://gateway-api.sigs.k8s.io/) project, including authorization
+policy and dynamic request routing. In many Kubernetes clusters, these CRDs are
+already available, but if they aren't, you will need to install it first.
+
+Follow [these instructions](../features/gateway-api/) for determining if the
+Gateway API is installed or how to install it.
+
 ## Prerequisite: generate mTLS certificates
 
 To do [automatic mutual TLS](../features/automatic-mtls/), Linkerd requires
@@ -40,15 +50,11 @@ intended. Instrunctions are on the
 
 ### linkerd-crds
 
-The `linkerd-crds` chart sets up the CRDs linkerd requires. If the Gateway API
-has already been installed on the cluster, you must specify
-`--set installGatewayAPI=false` or add this to the `values.yml` in order to
-avoid a conflict. See [the Gateway API](../features/gateway-api/) for more
-details.
+The `linkerd-crds` chart sets up the CRDs linkerd requires:
 
 ```bash
 helm install linkerd-crds linkerd-edge/linkerd-crds \
-  -n linkerd --create-namespace --set installGatewayAPI=false
+  -n linkerd --create-namespace
 ```
 
 {{< note >}}

linkerd.io/content/2.19/tasks/install.md

@@ -37,6 +37,13 @@ local machine, or even somewhere else.
 Make sure that your Linkerd version and Kubernetes version are compatible by
 checking Linkerd's [supported Kubernetes versions](../reference/k8s-versions/).
 
+Linkerd also requires the [Gateway API](https://gateway-api.sigs.k8s.io/) CRDs.
+In many Kubernetes clusters, these CRDs are already available, but if they
+aren't, you will need to install it first.
+
+Follow [these instructions](../features/gateway-api/) for determining if the
+Gateway API is installed or how to install it.
+
 Before installing the control plane, validate that this Kubernetes cluster is
 configured appropriately for Linkerd by running: