Running in to issues deploying with Kubernetes usi...
# prefect-server
s
Running in to issues deploying with Kubernetes using the default helm chart, enabling the tenant and the agent. The tenant and agent pods are having issues connecting. Agent logs ending with…
Copy code
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='<my-deployment-name>-apollo.<namespace>', port=4200): Max retries exceeded with url: /graphql (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fb5d1bd6510>: Failed to establish a new connection: [Errno -2] Name or service not known'))
Tenant pod logs ending with…:
Copy code
File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 516, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=4200): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd0c274e990>: Failed to establish a new connection: [Errno 111] Connection refused'))
Not sure which settings need to be updated in the values.yaml file, but it’s gotta be something…
m
Hello Sam! Do you have network policies in your cluster which could prevent agent and tenant to connect to api?
s
I’m asking the people who know kubernetes way more than I do this one!
I can see in the UI that I can connect to the graphql endpoint, so I want to say no, but I’ll verify.
👍 1
@Mariia Kerimova I was able to get the helm chart to work correctly by using a specific image in the
createTenant
job and the
agent
. I specified tag
0.15.4
, and it worked fine. I think something in v
0.15.5
may have borked this one. The tenant was attempting to connect to
localhost
rather than the correct apollo endpoint.
m
Hi Sam! Oh, thank you for letting me know, I'll check with the team, and open an issue in server repo if needed 👍