@kapa.ai Airbyte version 1.6 introduced a breaking change for service account permissions. If you're a Self-Managed Enterprise customer upgrading from 1.5.1 or earlier to 1.6 or later, follow the directions in this article before you upgrade to 1.6. If you're a Self-Managed Community user, this information isn't relevant to you. Learn more about service accounts. what is service account

A service account in the context of Airbyte (and Kubernetes) is an identity used by applications running within your Kubernetes cluster to interact with the Kubernetes API and other resources. Service accounts are used to control and grant permissions for these applications, such as allowing Airbyte to access secrets, manage pods, or perform other operations required for its functionality. In Airbyte Self-Managed Enterprise, starting from version 1.6, the service account used by Airbyte must have additional permissions, specifically access to the "secrets" resource, to complete upgrades and operate correctly. If you are using Airbyte's default service account (

airbyte-sa

), or a custom one defined in your

values.yaml

, you must ensure it has the necessary permissions before upgrading to 1.6 or later. Otherwise, the upgrade will fail and Airbyte will not start properly until the permissions are updated. More details on service accounts in Kubernetes can be found in the [Kubernetes documentation](https://kubernetes.io/docs/concepts/security/service-accounts/) and in the Airbyte upgrade guide for service accounts [here](https://docs.airbyte.com/platform/enterprise-setup/upgrade-service-account) and [here](https://docs.airbyte.com/platform/1.6/enterprise-setup/upgrade-service-account).