# Managing Gateway API resources

When BEL is installed with Helm or BEL's lifecycle operator, it 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.

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.

> [!NOTE]
> **Note:** When BEL is installed using the CLI, the Gateway
> API resources are not installed by default.

**Helm:**

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

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

**Lifecycle operator:**

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

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

## Learning more

For more information about managing the Gateway API, see the [Gateway API
support](https://linkerd.io/2.18/features/gateway-api/)
page at linkerd.io.
