Klemens Kasseroller

07/06/2022, 1:28 PM
Hi! While trying to launch workflows from the flyte console, I experienced timeouts with the error message "Request failed with status code 504" coming from the flyte admin after 15s. I figured out, that the problem occurs if the inputs and outputs of the individual tasks are complex/nested dataclasses. Could someone explain to me, what is happening behind the scenes, when launching a (static) workflow, and why the structure of my inputs and outputs matters at that point in time. Does anyone know a solution to this problem? I am using the sandbox deployment (not the DinD deployment) on a local Kubernetes cluster (tested both on a Windows laptop and on a Linux workstation). Chart versions:
I was able to solve this problem by overriding the flyteadmine image version in the flyte-core chart:
Copy code
  repository: <|>
  tag: v1.1.29-hotfix
  pullPolicy: IfNotPresent