-
Notifications
You must be signed in to change notification settings - Fork 230
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
Helm chart v2.0.0-rc2 fails to install on fresh k8s 1.18.8 #88
Comments
I'll take a look at this and have created #87 to avoid this in the future |
Interestingly I have the same issue with version 2.0.0-rc2, but it's working fine with version 2.0.0-rc |
@ahmelsayed do you have bandwidth to help here? |
Discussed in standup - hoping to get rid of the problem. @tomkerkhove shipped @TsuyoshiUshio / @ahmelsayed let me know if you can help look at this. I may be able to spend some cycles tonight as well |
I can give a hand here as well, will check it out later today |
Thanks @arschles! |
Awesome guys. @arschles let me know if you can't find the time and I'll try to fix it during the weekend. |
Can confirm that 2.0.0-rc3 works, but it isn't published to the index so had to clone. Let me clean it up a little and publish |
I have met this problem today as well. Difference is I was updating keda-2.2.0 to keda-2.2.2.
I had searched on Internet, I found that is because the newer version's chart template crd(CustomResourceDefinition) already exist(highly likely from your installed versions before) in your k8s api resources and they had a conflict. Below is my steps what I have done(I used helm 3):
now, conflict resource still here:
Delete them by kubectl delete:
Run it again you would find all of the template resource was deleted:
Try use kubectl api-resources to check, we found it's clear:
4 reinstall and successful:
Problem I have met in this process:
About how to fix the conflict resource in helm, I referred this article: At last, hope my article can be helpful to whom met this problem! |
Thanks for the write-up, if I get it correctly it's just due to Helm 3, right? |
I am not sure what will happened in Helm2, but in my case, yes, I used Helm 3. |
Signed-off-by: Jan Wozniak <[email protected]>
Attempting to install the chart fails with error
Expected Behavior
It is able to install on a fresh cluster
Actual Behavior
It does not install
Steps to Reproduce the Problem
Specifications
The text was updated successfully, but these errors were encountered: