The Kafka Connect Build is currently running under the default service account. That might make it harder to assign it some special rights (such as push credentials assigned in a different way than Kubernetes secret - for example using AWS IAM). Or the opposite way - give it right it should not have but which might be already given to the default service account.