https://prefect.io
Join Slack
Are there plans to add prefect-server helm chart to a helm repository?
# prefect-server
p
Are there plans to add prefect-server helm chart to a helm repository?
m
Hello Pedro! Yes, it will be added to a helm repository pretty soon. Stay tuned! 🙂
p
🙌
z
Yeah we just want its behavior to be more clearly established before versioning it and right now we’re still exploring how it’s used/deployed across different cloud providers.
❤️ 1
p
@Michał D
j
Revisiting this... I'm about to install Prefect on our Kubernetes dev cluster, and I'm about to create a custom Helm chart for Prefect, but I'd rather use something built "officially" (even if it's in alpha stage). Was there any progress on this front?
z
Hey Jay, I'm out of office right this second but I intend to push it to a helm repository by early March and it's definitely ready to use pulled from our Server repo.
j
z
Yep!
🙌 1
j
Thanks!! And have a good day off 🙂
Hello! Following up on this, I run into an issue while deploying the Helm chart with Prefect version 
0.14.10
. The default Docker image seems to be missing the 
kubernetes
PIP package:
Copy code
Traceback (most recent call last):
  File "/usr/local/bin/prefect", line 8, in <module>
    sys.exit(cli())
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/prefect/cli/agent.py", line 288, in start
    start_agent(KubernetesAgent, image_pull_secrets=image_pull_secrets, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/prefect/cli/agent.py", line 108, in start_agent
    agent = agent_cls(labels=labels, env_vars=env_vars, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/prefect/agent/kubernetes/agent.py", line 121, in __init__
    from kubernetes import client, config
ModuleNotFoundError: No module named 'kubernetes'
Is there a special Docker image we should be using? I'm currently using 
prefecthq/server:core-0.14.20
z
Hey @Jay Vercellone -- what command/code you running that's giving you this error?
j
Those are the logs of the 
prefect-server-agent
pods. I fixed it by setting the tag of the 
prefecthq/prefect
image to 
0.14.20
instead of 
core-0.14.20
😄
In my 
values.yaml
file:
Copy code
agent:
  enabled: true
  image:
    tag: 0.14.20
z
Yeah by default it would not include the 
core-
bit because that image does not include orchestration extras
j
Correct. The reason I included the 
core-
prefix in the first place was because some of the images (like 
prefecthq/server
) are only published under such tags.
Anyway, it seems to be working fine :) I particularly liked all the documentation in the 
values.yaml
file, super helpful!
z
Ah I see--I'll make a note to fix this when I do the helm-repo work.
Good to hear 🙂
j
@Zanie I submitted a PR with a small fix for the Helm charts: https://github.com/PrefectHQ/server/pull/201 It's a fix for an issue that appears when the deployment is set to execute the "create tenant" job, and the Apollo service is set with a port other than the default 
4200
2 Views
Open in Slack
PreviousNext
Powered by

Prefect Community

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.

Powered by