Summary
The user encountered an error with the service account in the orchestrator-repl pod after updating AWS keys. The error was related to the service account not being found, but was resolved by setting the service account name to ‘airbyte-admin’.
Question
After I have overwritten the AWS Keys on the orchestrator-repl pod, now I was having a different error.
Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. pods \"destination-s3-write-6-1-xwqdz\" is forbidden: error looking up service account airbyte/airbyte-admin: serviceaccount \"airbyte-admin\" not found
So it seems the service account must be named airbyte-admin. Despite I have set a custom name through global.serviceAccountName and global.serviceAccount.name.
After I updated the serviceAccount.name to airbyte-admin everything worked like a charm!
Now orchestrator-repl is using the right service account/role instead of static AWS keys!
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.