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, insure 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, set the enableHttpRoutes=false flag when installing the CRDs:

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

Helm

When installing BEL with Helm, set the enableHttpRoutes=false Helm value when installing the linkerd-crds Helm chart:

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

Lifecycle operator

When configuring BEL’s lifecycle operator, you must set enableHttpRoutes: false in the Control Plane manifest:

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 page at linkerd.io.