Hello everyone! First time user here but excited t...
# ask-community
l
Hello everyone! First time user here but excited to get going. I'm installing into kubernetes via helm and I'm not able to get the chart to create a tenant. It looks like its expecting apollo on localhost:4200 but its running in a different pod so I keep getting connection issues. Thoughts?
👋 2
👍 1
n
Hi @Lon Nix - how are you attempting to create the tenant? You can create a default tenant automatically by adding the flag
--set jobs.createTenant.enabled=true
; otherwise you’ll want to call
prefect backend server && prefect server create-tenant --name <<name>> --slug <<url_slug>>
after setting:
Copy code
[server]
  host = "http://<apollo pod ip>"
in your local
~/.prefect/config.toml
file
l
I went with
--set jobs.createTenant.enabled=true
(using values.yaml) and it created the job that attempted to create the tenant but all I got was this
Copy code
<stack trace>
requests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=4200): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f5ab3a00e90>: Failed to establish a new connection: [Errno 111] Connection refused'))
I'm not sure why its using localhost, apollo is running in its own pod
There's an option for the UI to specify the apollo url if not localhost:4200 but that doesn't seem to be possible for the job
n
Do you have the apollo ingress enabled?
l
no, I am not using ingress. I can if that'll solve this but from what I can tell it'll still try localhost:4200
I got things working through the UI, its all proper except the tenant
n
Let me see if I can grab some help with this one, it sounds like you’ve got the proper setup so maybe there’s a missing piece
👍 1
l
thanks. From my very very very limited experience with this I would expect there to be something like
jobs.createTenant.appoloApiUrl
to set so that I can tell it where to find apollo. Hopefully
localhost:4200
isn't hardcoded
👍 1
n
Can you confirm which version of Prefect you’re using?
l
the
latest
tag. I have not locked down a version yet
n
Ok great, thanks for confirming - I’ll check with the team and get back to you
Hi @Lon Nix - this looks like a bug with
latest
- can you give this PR a try and let me know if it fixes your issue?
👍 1
l
will I need to build the image myself from that branch?
n
I don’t think that changes any of the images, just the
yaml
spec
l
ah, gotcha
worked like a charm! thanks!
n
Awesome!