Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

hi everyone! i have one silly doubt. when we run a orion server locally how do we access the ui .
<http://127.0.0.1:4200> this just give me 404
also can we run prefect orion on k8s and use that to create infra blocks, flow deployments  as well as run deployments ?

Hi Deepanshu, there are a number of docs available for running Orion on K8s in discourse and docs - which cloud are you using ?

If you run Orion server locally, it should be available on 4200 locally . If you are getting a 404, it could be dns / networking on your local host , as I pretty commonly test using local host 

<https://github.com/PrefectHQ/prefect-helm> can be used to deploy into your existing EKS cluster

if you don’t use helm and just want a basic / standard config, you can run `prefect kubernetes manifest orion` to generate a deployment manifest which can be used to apply to the EKS cluster

<@U03FKQX1TH9> getting lot of postgres database issues. can you share the prefect image that we should use ?

```INFO:     Application startup complete.
INFO:     Uvicorn running on <http://0.0.0.0:4200> (Press CTRL+C to quit)
Unexpected error in: TimeoutError()
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/cachetools/__init__.py", line 68, in __getitem__
    return self.__data[key]
KeyError: 'TELEMETRY_SESSION'

  File "asyncpg/protocol/protocol.pyx", line 201, in bind_execute
asyncio.exceptions.TimeoutError
debug2: channel 0: window 995443 sent adjust 53133```


Unless you have some specific reason otherwise, I’d suggest the latest

image.png

can you share some working kubernetes yaml if possible  or any docker run command ?

you can get a default manifest from the CLI:
`prefect kubernetes manifest orion` for the server, and `prefect kubernetes manifest agent` for the agent

Although bad file descriptor on a socket seems like some odd behavior