@kapa.ai As of version 1.6 of the Airbyte Platform, we require your Service Account permissions to include access to the "secrets" resource

As of version 1.6 of the Airbyte Platform, your Kubernetes service account must have permissions to access the "secrets" resource. This is a breaking change introduced in 1.6 for Self-Managed Enterprise deployments. If you attempt to upgrade from 1.5.1 or earlier without updating your service account permissions, the Bootloader pod will fail to start, and you will see an error indicating that access to the "secrets" resource is required. To resolve this, you need to update your service account or role to include the "secrets" resource in its permissions. If you are using Airbyte's default service account (

airbyte-sa

), you can patch the role with the following command:

sh kubectl -n <namespace> patch role airbyte-admin-role --type='json' -p='[{"op": "replace", "path": "/rules/0/resources", "value": ["jobs", "pods", "pods/log", "pods/exec", "pods/attach", "secrets"]}]'

If you are using your own service account, ensure your role includes the "secrets" resource, for example:

yaml apiVersion: <http://rbac.authorization.k8s.io/v1|rbac.authorization.k8s.io/v1> kind: Role metadata:   name: roleName rules:   - apiGroups: ["*"]     resources: ["jobs", "pods", "pods/log", "pods/exec", "pods/attach", "secrets"]     verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]

After updating the permissions, you can proceed with the upgrade to Airbyte 1.6 or later. If you do not update the permissions, the upgrade will not proceed, but your existing Airbyte installation will continue to function until you are ready to update the permissions and complete the upgrade process. For more details, see the official documentation on [updating service account permissions for 1.6](https://docs.airbyte.com/platform/1.6/enterprise-setup/upgrade-service-account)