#3996 [BUG] flytescheduler Pod crashloops temporarily Issue created by gdabisias Describe the bug In the flyte-core deployment, the flytescheduler will crashloop a few times right after the deployment, trying to connect to flyte admin, which might not be ready to accept connections. After a few seconds things stabilise. error:

panic: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp <http://xxx.xxx.xxx.xxx:81|xxx.xxx.xxx.xxx:81>: connect: connection refused"

We should wait until the flyteadmin is up and running, before trying to connect to it. Expected behavior No crash loop of the flytescheduler at start Additional context to reproduce Logs from the

flytescheduler

pod show:

panic: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp <http://xxx.xxx.xxx.xxx:81|xxx.xxx.xxx.xxx:81>: connect: connection refused"

Apparently, the scheduler connects to the flyteadmin before the flyteadmin is up and healthy; after a few retries it succeeds, so we should wait for the admin to be up before starting the scheduler Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte