✗ Helm upgrade failed: pre-upgrade hooks failed: pod airbyte-airbyte-bootloader failed

Based on the information provided in the extracts, it seems like you're encountering an issue with the Airbyte bootloader during the Helm upgrade process. This issue might be due to various reasons such as configuration errors, resource constraints, or network issues. Here are a few steps you can take to troubleshoot this issue: 1. Check the logs of the

airbyte-airbyte-bootloader

pod to get more details about the error. You can do this by running the command

kubectl logs airbyte-airbyte-bootloader -n airbyte

as shown in the [forum post](https://discuss.airbyte.io/t/3127). 2. Check the status of all the pods in the

airbyte

namespace by running

kubectl get pods -n airbyte

. This can help you identify if there are any other pods that are not running as expected. 3. Check the events in the

airbyte

namespace sorted by the last timestamp by running

kubectl -n airbyte get events --sort-by='{.lastTimestamp}'

. This can provide more insights into what might be causing the issue. If you're still unable to resolve the issue, I recommend reaching out to the Airbyte community on their [forum](https://discuss.airbyte.io) or [Slack](https://airbytehq.slack.com) for further assistance. You can also consider submitting a support ticket if you're using Airbyte Enterprise or have an OSS support package, as mentioned in the [documentation](https://docs.airbyte.com/operator-guides/contact-support).

@kapa.ai java.lang.RuntimeException: Cannot upgrade from version 0.0.99 to version 0.50.32 directly. First you must upgrade to version 0.32.0-alpha. After that upgrade is complete, you may upgrade to version 0.50.32. at io.airbyte.bootloader.Bootloader.assertNonBreakingMigration(Bootloader.java:149) ~[io.airbyte-airbyte-bootloader-0.50.32.jar:?] at io.airbyte.bootloader.Bootloader.load(Bootloader.java:103) ~[io.airbyte-airbyte-bootloader-0.50.32.jar:?] at io.airbyte.bootloader.Application.main(Application.java:22) ~[io.airbyte-airbyte-bootloader-0.50.32.jar:?]

The error message you're seeing indicates that you cannot upgrade directly from version 0.0.99 to version 0.50.32. You first need to upgrade to version 0.32.0-alpha-patch-1, and then you can upgrade to version 0.50.32. This is due to breaking changes made in version v0.32.0-alpha-patch-1, and the logic for these changes is removed in later versions, making it impossible to upgrade directly. Here are the steps to upgrade to v0.32.0-alpha-patch-1: 1. If you are in a cloned Airbyte repo, v0.32.0-alpha-patch-1 can be pulled from GitHub with the following command:

bash git checkout v0.32.0-alpha-patch-1

2. If you are running Airbyte from downloaded

docker-compose.yaml

and

.env

files without a GitHub repo, run the following command to pull this version and overwrite both files:

bash wget -N <https://raw.githubusercontent.com/airbytehq/airbyte/v0.32.0-alpha-patch-1/{.env,flags.yml,docker-compose.yaml}>

If you use custom connectors, this upgrade requires all of your connector specs to be retrievable from the node running Airbyte, or Airbyte will fail on startup. If the specs are not retrievable, you need to fix this before proceeding. Alternatively, you could delete the custom connector definitions from Airbyte upon upgrade by setting the

VERSION_0_32_0_FORCE_UPGRADE

environment variable to true. This will cause the server to delete any connectors for which specs cannot be retrieved, as well as any connections built on top of them. After you have successfully upgraded to v0.32.0-alpha-patch-1, you can then proceed to upgrade to version 0.50.32. For more details, please refer to the [Airbyte upgrade guide](https://docs.airbyte.com/operator-guides/upgrading-airbyte).