calm-zoo-68637
08/09/2023, 6:43 PMserviceAccount.imagePullSecrets[0].name
? Here's what I see when describing the service account (it would show "not found" if the secret didn't exist):
kubectl describe sa flyte-flyte-binary -n flyte
Name: flyte-flyte-binary
Namespace: flyte
Labels: <http://app.kubernetes.io/instance=flyte|app.kubernetes.io/instance=flyte>
<http://app.kubernetes.io/managed-by=Helm|app.kubernetes.io/managed-by=Helm>
<http://app.kubernetes.io/name=flyte-binary|app.kubernetes.io/name=flyte-binary>
<http://app.kubernetes.io/version=1.16.0|app.kubernetes.io/version=1.16.0>
<http://argocd.argoproj.io/instance=flyte|argocd.argoproj.io/instance=flyte>
<http://helm.sh/chart=flyte-binary-v1.8.1|helm.sh/chart=flyte-binary-v1.8.1>
Annotations: <none>
Image pull secrets: ecr-image-pull-secret
tall-lock-23197
calm-zoo-68637
08/10/2023, 1:14 PMcalm-zoo-68637
08/10/2023, 1:43 PMflyte-development
2. Update the default service account in the development namespace to have access to those secrets
I don't love this solution since it means if the people using Flyte ever want to create a project that is not called "flyte" I will need to update all my terraform templates to populate secrets for themtall-lock-23197
freezing-boots-56761
freezing-boots-56761
calm-zoo-68637
08/11/2023, 3:41 PMfreezing-boots-56761
freezing-boots-56761
freezing-boots-56761
calm-zoo-68637
08/13/2023, 8:58 PMfreezing-boots-56761
calm-zoo-68637
08/14/2023, 12:24 AMfreezing-boots-56761