New RunLLM response generated: >>>*# Question* Hi all, I was wondering if anyone experienced any problems with using Azure Blob Storage as flyte storage? It works great for "normal" tasks, but when I define a dynamic workflow, then there are some additional containers started before executing the actual workflow tasks, and those containers do not get azure credentials and are failing. # Answer This issue is related to how Flyte handles Azure Blob Storage credentials for dynamic workflows. The problem arises because the additional containers started by Flyte for dynamic workflows do not inherit the necessary Azure credentials. According to the Flyte GitHub issue #3962, the current workaround involves manually setting environment variables like

AZURE_STORAGE_ACCOUNT_NAME

and

AZURE_STORAGE_ACCOUNT_KEY

in your PodTemplate. This ensures that the credentials are available to all containers, including those started for dynamic workflows. Would you like more details on how to set up these environment variables in your PodTemplate? Sources: - Flyte GitHub issue #3962 Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1720188290.854929 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.