# Upgrading BEL using the lifecycle automation operator

In this guide, we'll show you how to perform zero-downtime upgrades for BEL
using its [lifecycle automation capabilities](/buoyant-enterprise-linkerd/2.15/features/operator/).

> [!NOTE]
> This guide assumes that your Linkerd installation was
> originally installed with BEL's lifecycle automation operator. If that's not the
> case, see our
> [migration guide](/buoyant-enterprise-linkerd/2.15/guides/migrating-to-bel-lifecycle-automation/).

## Step 1: Upgrade your lifecycle automation operator

The latest versions of BEL sometimes requires the latest version of the
lifecycle automation operator for support. Thus, our recommendation is that
before upgrading BEL itself, you upgrade the operator to the latest version.

The lifecycle automation operator is part of the
[Buoyant Extension](/release-notes/buoyant-extension/). See the release notes
for each Buoyant Extension release for a list of installable BEL versions.

Start by updating the Buoyant Extension:

```bash
helm repo add linkerd-buoyant https://helm.buoyant.cloud
helm repo update
helm upgrade linkerd-buoyant \
  --namespace linkerd-buoyant \
  --reuse-values \
  linkerd-buoyant/linkerd-buoyant
```

## Step 2: Update the control plane CRD

With the latest lifecycle automation operator installed, we are ready to upgrade
BEL itself. At this point, it's simply a matter of changing the version of BEL
specified in the `ControlPlane` resource.

Typically this would be done by a gitops workflow using a tool such as Argo or
Flux. However, it can also be done directly on the cluster, e.g. by running:

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

The ControlPlane resource contains a `version` key (see
[the full reference guide](/buoyant-enterprise-linkerd/2.15/reference/operator/)) that looks like this:

```yaml
apiVersion: linkerd.buoyant.io/v1alpha1
kind: ControlPlane
metadata:
  name: linkerd-control-plane
spec:
  components:
    linkerd:
      version: enterprise-2.15.7
      license: ...
...
```

> [!NOTE]
> **Note:** If you're upgrading from stable-2.14 or
> enterprise-2.14, ensure you've added a `license` field with your license key
> from the [Buoyant portal](https://enterprise.buoyant.io/).

Set the `version` key in this resource to the desired BEL version (e.g.
`enterprise-2.15.7`), and BEL's lifecycle automation operator will take
care of the rest. It will first upgrade the Linkerd core control plane, and once
that successfully completes, the data plane operator will restart each workload
selected by the `DataPlane` resources, so that the pods will pick up a new
version of the Linkerd proxy.

## Step 3: Verifying the lifecycle automation operator status

The lifecycle automation operator will typically take several minutes to
complete an upgrade. You can monitor its progress by getting its Kubernetes
status:

```bash
kubectl get controlplane
```

You should see output similar to this:

```bash
NAME                    STATUS     DESIRED             CURRENT             AGE
linkerd-control-plane   Pending    enterprise-2.15.7   enterprise-2.xx.0        116s
```

Once the control plane moved from `Pending` to `UpToDate`, you can check the
status of the data plane:

```bash
kubectl get dataplane -A
```

```bash
NAMESPACE         NAME        STATUS     DESIRED   CURRENT   AGE
emojivoto         dataplane   UpToDate   4         4         4s
linkerd-buoyant   dataplane   UpToDate   3         3         4s
```
