https://flyte.org logo
Join Slack
Powered by
I might have missed this in the docs, but is it ex...
# flyte-support
e
I might have missed this in the docs, but is it expected that the flyte backend is backwards-compatible with older 
flytekit
versions? We have some other dependencies blocking upgrading 
flytekit
presently, but would like to keep the backend services as up-to-date as possible
t
back to 1.0 of flytekit yeah
🙏 1
e
Fantastic, thanks for confirming @thankful-minister-83577
Hmm, it unfortunately looks like there were some incompatibilities between the 1.3.0 chart & flytekit 1.2.7 (we were unable to run any dynamic steps that fanned out/those tasks just stalled)
t
those should definitely be compatible.
why can’t you upgrade flyte btw? what are the dependency issues you’re seeing?
e
We're unfortunately blocked on protobuf due to another dependency (hilariously enough, kubeflow pipelines)
t
can you pull the futures file for the stalled tasks?
e
Ripping kubeflow out of our codebase soon, but right now the dependency constraints on protobuf aren't compatble
t
so protobuf 3
e
What's the futures file? Happy to look for it
t
yeah
well maybe just look at the admin endpoint, that might be easier.
e
Sorry, could you clarify? What should I be looking at?
t
sorry afk
e
So just saw some more interesting behavior - we also hit this after rolling back, but in this particular situation we had 3 concurrently running dynamic workflows (that in turn all had >500 nodes in the pipeline). it took approx. an hour for the actual dynamic step to complete & fan-out, but all of them are now executing
163 Views
Open in Slack
PreviousNext
Powered by