Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

:wave:  We're currently seeing 503's trying to pull the flyte containers:
`GET <https://cr.flyte.org/v2/>: unsupported status code 503`
Is the team aware?

<@U02F9HC76S2> can you share the image id?

```container_pull(
    name = "flyte-admin",
    digest = "sha256:7796509f6e221420c1b3aac0db8682cbd201e456dd64bc9d4813d77bc1104a02",
    registry = "<http://cr.flyte.org|cr.flyte.org>",
    repository = "flyteorg/flyteadmin",
    tag = "v1.1.118",
)```

<@U02F9HC76S2> i can download it
```(flytekit) ➜  extras git:(main) ✗ docker pull <http://cr.flyte.org/flyteorg/flyteadmin:v1.1.118|cr.flyte.org/flyteorg/flyteadmin:v1.1.118>                                                                                                                                                                                                                                                                                                                                                                                             &lt;aws:open-compute&gt;
v1.1.118: Pulling from flyteorg/flyteadmin
bdb2de7ba06c: Pull complete
169be228a0fd: Pull complete
7d8e6ee43ac1: Pull complete
640c5a015283: Pull complete
Digest: sha256:971ece1d6499e0bfa553b5da5939087b90d275172408a06f4edd79dc85fbfa4a
Status: Downloaded newer image for <http://cr.flyte.org/flyteorg/flyteadmin:v1.1.118|cr.flyte.org/flyteorg/flyteadmin:v1.1.118>
<http://cr.flyte.org/flyteorg/flyteadmin:v1.1.118|cr.flyte.org/flyteorg/flyteadmin:v1.1.118>```

I think this is something to do with your internal policy?

or 503 seems like throttling - github might be throttling

We are getting too many flyteadmin container downloads right now

yep — things seem to be working again. Apologies for the ping!