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

Hello, I’m experiencing another issue during the deployment of the prefect helm chart. 
```Error from server (BadRequest): container “graphql” in pod “prefect-poc-graphql-76462537d4-4v7c6” is waiting to start: PodInitializing```
All other pods seems to be deployed and running well. Anyone knows why this is happening? Also, my UI is not showing up as well, probably due to this issue.

```$ kubectl logs prefect-poc-graphql-76498785d4-4v7c6 -n dse-default db-upgrade

Running Alembic migrations...

INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.

INFO  [alembic.runtime.migration] Will assume transactional DDL.

 

Could not upgrade the database!

Error: HTTPConnectionPool(host='prefect-poc-hasura.default', port=3000): Max retries exceeded with url: /v1/query (Caused by NewConnectionError('&lt;urllib3.connection.HTTPConnection object at 0x7f6dcb087390&gt;: Failed to establish a new connection: [Errno -2] Name or service not known'))
$ kubectl logs prefect-poc-graphql-76498785d4-4v7c6 -n dse-default db-upgrade

 

Running Alembic migrations...

INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.

INFO  [alembic.runtime.migration] Will assume transactional DDL.

 

Could not upgrade the database!

Error: HTTPConnectionPool(host='prefect-poc-hasura.default', port=3000): Max retries exceeded with url: /v1/query (Caused by NewConnectionError('&lt;urllib3.connection.HTTPConnection object at 0x7f6dcb087390&gt;: Failed to establish a new connection: [Errno -2] Name or service not known'))```

Seems like graphql is looking for at the hasura service in ‘default’ namespace, instead of ‘dse-default’ (the namespace that the hasura service is in). How do I change this configuration?

Solved the issue by specifying namespace when deploying helm chart