👋 Some sanity checks on Flyte deployments
1. The current
flyte-binary helm chart only supports using
s3
and
gcs
storage backends, correct? I saw
this discussion post that showed an alternate way to configure
stow
with Azure, but it is unclear which chart is being used (I assume the
flyte one). Reading the
flyte-binary
chart source, I can't see how any other backend is possible.
2. The
stow
sdk only supports using those unfortunate azure shared keys (
stow code referenced here). Is this right, or should I be looking somewhere else to enable AD auth. Ideally we'd want Flyte's storage auth do the simple
azidentity.NewDefaultAzureCredential(nil)
thing so Azure Workload Identity can be used.