[Housekeeping] Enable flyte-core to consume pre-created secrets

[davidmirror-ops]

Describe the issue

In a multi-cluster deployment using flyte-core, one of the steps in the docs indicate to manually create a secret containing the tokens and certs for each dataplane cluster and then submit it to the control plane cluster.

This is inconvenient for automated deployments.

Instead, similar to the flyte-binary chart, if flyte-core is capable of consuming pre-created secrets, automation could override the values and mount the necessary secrets for each dataplane cluster.

What if we do not do this?

Otherwise, users will still have to either rely on an external tool or create secrets manually.

Related component(s)

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[github-actions]

Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable.
Thank you for your contribution and understanding! 🙏