# Managing Gateway API resources

Linkerd, by default, will create, update, and delete Gateway API resources as
required. Because of this, any other tools on your system that use Gateway API
resources will be need to be compatible with the version of the Gateway API that
Linkerd installs.

When BEL is installed, you may prefer to have something other than Linkerd
manage the Gateway API resources on your cluster. To do this, ensure that the
Gateway API resources are installed first, then you will need to instruct
Linkerd not to manage the Gateway API resources.

**CLI:**

When [installing BEL using the CLI](/buoyant-enterprise-linkerd/2.17/installation/#step-2-install-bel), set
the `enableHttpRoutes=false` flag when installing the CRDs:

```bash
linkerd install --crds --set=enableHttpRoutes=false | kubectl apply -f -
```

**Helm:**

When
[installing BEL with Helm](/buoyant-enterprise-linkerd/2.17/installation/install-guide/#install-method=helm&install-bel-using-helm),
set the `enableHttpRoutes=false` Helm value when installing the `linkerd-crds`
Helm chart:

```bash
helm install linkerd-crds \
  --set enableHttpRoutes=false
  ...
```

**Lifecycle operator:**

When
[configuring BEL’s lifecycle operator](/buoyant-enterprise-linkerd/2.17/installation/install-guide/#install-method=operator&configure-the-lifecycle-operator),
you must set `enableHttpRoutes: false` in the Control Plane manifest:

```yaml
apiVersion: linkerd.buoyant.io/v1alpha1
kind: ControlPlane
metadata:
  name: linkerd-control-plane
spec:
  components:
    linkerd:
      crdsConfig:
        enableHttpRoutes: false
  ...
```

## Learning more

For more information about managing the Gateway API, see the [Gateway API
support](https://linkerd.io/2.17/features/gateway-api/#option-2-a-different-tool-manages-the-gateway-api)
page at linkerd.io.
