@kapa.ai, how to attach a service account to the replication jobs separately? I have deployed Airbyte 1.6.0 using helm chart on eks cluster.

To attach a specific Kubernetes ServiceAccount to the replication jobs (worker/workload pods) in a Helm-based Airbyte 1.6.0 deployment on EKS, you need to configure the Helm values that control the job service account. From the linked GitHub issues, the service account used by replication pods is driven by the

JOB_KUBE_SERVICEACCOUNT

env var on the

airbyte-workload-launcher

and worker pods, and this is set via Helm values. One user fixed the “airbyte-admin not found” problem by explicitly setting the global jobs service account name in

values.yaml

as follows:

yaml global:   jobs:     kube:       serviceAccountName: <your-service-account-name>

This causes

JOB_KUBE_SERVICEACCOUNT

to be set to your service account and the replication pods to run under that account instead of the default

airbyte-admin

/

airbyte-sa

combination. [[helm SA issue](https://github.com/airbytehq/airbyte/issues/49938)] If you’re also using IRSA, make sure your ServiceAccount has the proper AWS IAM role annotation and RBAC permissions (including

jobs

,

pods

,

pods/log

,

pods/exec

,

pods/attach

, and

secrets

for 1.6+). [[upgrade SA 1.6](https://docs.airbyte.com/platform/1.6/enterprise-setup/upgrade-service-account)]

@kapa.ai adding service account parameter under global > jobs > kube would create service account for me?

A message from kapa.ai