New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to Deploy on Polyaxon with helm v2.16.0 (No kind Job is registered for version batch/v1) #601
Comments
Hi, that's because the the distributed helm chart does not target support 1.16 yet. A fix has been already merged, and just need to be released. You can try to deploy Polyaxon directly based on the master branch https://github.com/polyaxon/polyaxon-chart A minor release will be pushed in the following days. |
Thanks for the fast reply @mouradmourafiq. Forgive the tedious question, but how would I go about deploying directly based on the master branch? EditI tried the following:
Which fails with the same error:
|
It turned out that the error you mentioned is related to a helm issue, downgrading to Helm 2.15.2 seems to fix it, on the helm part there's an open PR, so you should install helm version 2.15.2:
You will then to update tiller, try : |
I had to specify Thanks for all of your help! |
Great, I will close this issue and pin it as a reference for other people until the helm team fix the bug and release a new version. |
Describe the bug
Following the instructions here I have been unable to deploy on google cloud using GKE.
Unfortunately, the instructions provided here
no longer appear to be valid because the link for
click-to-deploy single-node file server
is no longer working (not clear this service is still available).To Reproduce
polyaxon admin deploy...
, which gives:Expected behavior
For Polyaxon to deploy.
Environment
I have tried updating the client version of
kubectl
to the latest version and the server version to the latest version that google currently provides (v1.14.8-gke.2
).Helm is the latest version (
v2.16.0
for client and server)Please let me know if can provided any additional information.
The text was updated successfully, but these errors were encountered: