Hey folks, I’m having a couple of problems using Metaflow on Azure. I had our DevOps team deploy Metaflow with Kubernetes using the instructions here. They then sent me the end-user setup instructions. Most things seem to work fine. I’m able to use the

@kubernetes

tag and pods spin up on our cluster for steps with the decorator. It also appears that all the flow artifacts are stored in our blob container. Scheduling with Argo also seems to work like a charm. The issues are using the

@conda

decorator and pulling artifacts from the Metaflow API. I’ll give some more detail for these below: 1. Whenever I use the @conda decorator for flows that have steps that run on Kubernetes, it’ll display:

Bootstrapping conda environment...(this could take a few minutes)

for several minutes until I eventually get

Internal error: Azure error: ('Connection aborted.', timeout('The write operation timed out'))

. I can run local flows with

@conda

and flows that have

@kubernetes

steps without issues, but the combination of both seems to cause the issue. 2. When using the Metaflow API, I can see all my flows just fine iterating through the

Metaflow

object, but when I pull out a run for a flow (

HelloFlow

) using

run = Run('HelloFlow/1')

and try

run.data

it’ll return

None

. Additionally, if I try to get the latest successful run from a flow object (

flow

) using

flow.latest_successful_run

, I’ll get the following error:

MetaflowInternalError: Azure error: Operation returned an invalid status 'This request is not authorized to perform this operation using this permission.'
ErrorCode:AuthorizationPermissionMismatch

I think that it’s possible that these are both permissions issues, but wanted to see if you all had some better insight before I pursue that. Thanks in advance!