---
# System prepended metadata

title: Airbyte upgrade process

---

# Airbyte upgrade process

Step 1: Check some previous MRs in the Datalake Gitlab repository for upgrading: https://gitlab.com/sourceability/data/datalake/-/merge_requests?scope=all&state=merged&search=upgrade. See what the usual changes were.
- kube/resources files often get changed.
- Change airbyte.env to reflect new version.
- Change copy-airbyte-config.sh to reflect new version.
- Change kustomization.yaml to reflect new container versions.

Step 2: Figure out what the latest release of Airbyte is: https://github.com/airbytehq/airbyte/releases
- 0.40.15

Step 3: Check the differences in .env and apply them to bases/airbyte/airbyte.env: https://github.com/airbytehq/airbyte/blob/master/.env

Step 4: Check the differences in the kustomization file and apply them to bases/airbyte/kustomization.yaml: https://github.com/airbytehq/airbyte/blob/master/kube/overlays/stable/kustomization.yaml

Step 5: Check the differences in kube/resources and apply them to bases/airbyte/kube/resources:
https://github.com/airbytehq/airbyte/tree/master/kube/resources

## Deployment 

Make sure to take a snapshot of the database before the new deployment.

Make sure that the `airbyte-mc` pod is deleted before the new deployment. The deployment is supposed to cover it, but sometimes it doesn't.

