# Configuring BEL's lifecycle automation

BEL provides [lifecycle automation for Linkerd](/buoyant-enterprise-linkerd/2.19/features/operator/) in the
form of a Kubernetes operator that runs on the cluster and allows for automated
installation and upgrades of Linkerd, across both control plane and data plane.

## Opt-in behavior

Lifecycle operator behavior is _opt-in_. Even with the operator running on the
cluster, it will not act on Linkerd unless configured to do so.

Operator behavior is determined by two custom resources: `ControlPlane` and
`Dataplane`. These work independently of each other; you may use one or both.

## Control plane configuration

It's easy to change the version of Linkerd that's running on your cluster by
changing the Linkerd version specified in the instance of the
[`ControlPlane` resource](/buoyant-enterprise-linkerd/2.19/reference/operator/#control-plane-configuration) on
your cluster:

```bash
kubectl edit controlplane/linkerd-control-plane
```

Once the version has been changed, the control plane operator will upgrade the
Linkerd core control plane.

**Note:** Each release of the operator supports a range of Linkerd versions to
which it can upgrade. In air-gapped environments, the Linkerd versions are fixed
at the time the operator was released. In non-air-gapped environments, the
operator is often capable of dynamically upgrading to Linkerd versions published
_after_ the operator itself was published. This reduces the need to upgrade the
operator in these environments. To see what range of Linkerd versions the
operator supports, see the
[Buoyant Extension release notes](/release-notes/buoyant-extension/).

## Data plane configuration

The `DataPlane` custom resources enable automatic upgrades of Linkerd proxies
running in your application workloads. This requires creating instances of the
[`DataPlane` resource](/buoyant-enterprise-linkerd/2.19/reference/operator/#data-plane-configuration) in each
namespace where Linkerd proxies are running on your cluster.

For instance, to opt-in all proxies in the `default` namespace:

```bash
kubectl apply -f - <<EOF
apiVersion: linkerd.buoyant.io/v1alpha1
kind: DataPlane
metadata:
  name: dp-update
  namespace: default
spec:
  workloadSelector:
    matchLabels: {}
EOF
```

When the control plane version changes or the proxy trust root doesn't match the
control plane, the data plane operator will restart each workload selected by
the `DataPlane` resources, one at a time, so that the proxies will be up to date
with the configuration of the control plane.

**Note:** If the identity issuer certificate changes, the workload will not be
restarted by the data plane operator because this change is automatically picked
up by the identity service.

## Walkthrough

[Video](https://vimeo.com/936766041)

## Learning more

- [Guide: Troubleshooting BEL's lifecycle automation](/buoyant-enterprise-linkerd/2.19/guides/troubleshooting-bel-lifecycle-automation/)
- [Lifecycle automation reference](/buoyant-enterprise-linkerd/2.19/reference/operator/)
- [Buoyant Extension release notes](/release-notes/buoyant-extension/)
