#3993 Fix flyte-core helm charts for multi cluster configuration Pull request opened by gdabisias While testing the flyte-core deployment, I found that there is an issue with secrets access describe in the Flyte multicluster guide. Basically we are creating manually a secret called

cluster-secrets

, but this does not get mounted properly by the services that are supposed to read from it, resulting in a PANIC error in

syncresources

service and in the

sync-cluster-resources

init container of the flyte admin service:

panic: Failed to get auth token: open /var/run/credentials/cluster_1_token: no such file or directory
failed to read k8s bearer token from configured path

I described the pods and notice that the secrets don't get mounted correctly and that we have a special case for when we actually add a multi cluster configuration

{{- if gt (len .Values.configmap.clusters.labelClusterMap) 0 }}
...

but that section is loading the

flyte-admin-secrets

secret instead of the new

cluster-secret

. This is a fix to have things working for how they are set up right now, but longer term there should not be this custom secret and we should have a pre-created secret in the charts that gets filled in by users from the

values-eks.yaml

file or something similar (e.g. reuse

flyte-admin-secrets

) Tracking issue This issue is linked to #3970 but is not fixing that Check all the applicable boxes ☑︎ I updated the documentation accordingly. -> No documentation to update ☑︎ All new and existing tests passed -> Tested this in a real world multicluster setup ☑︎ All commits are signed-off. flyteorg/flyte ✅ All checks have passed 2/2 successful checks

#3993 Fix flyte-core helm charts for multi cluster configuration Pull request merged by davidmirror-ops flyteorg/flyte