-
Notifications
You must be signed in to change notification settings - Fork 2k
Upgrading helm chart from v1.0.2 to v1.1.0: failed to list *v1.TransportServer: #4856
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
Comments
Hi @kyrofa thanks for reporting! Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂 Cheers! |
@kyrofa You should be able to install 1.0.2, then upgrade the CRDs (our docs walk through it), followed by upgrading to 1.1.0 of the chart. i just did a quick test in my lab and it worked out as expected. Let us know how it goes. |
Wait, so the helm chart installs the CRDs, but it doesn't update them? That's confusing, I'm not sure I've ever used a chart that worked that way. Is there a reason the helm chart doesn't update them for me if I don't install with |
https://helm.sh/docs/chart_best_practices/custom_resource_definitions/ We are always looking for ways to make this better. |
Ah, yes indeed, rook is a good example. I'm not going to lie though, I didn't actually know about this helm limitation until just now. I've never written a helm chart, so I've never read that part of the docs. I'll need to take a closer look at some other charts I'm using, so thanks for schooling me. This is a surprisingly sharp edge, honestly: every chart that uses CRDs needs to explicitly document this behavior (in general they don't). Also, it's not unusual for chart users to not even realize that their chart installs CRDs in the first place, so this requires a deeper knowledge of the chart than most users will have. nginx is a good example: I don't actually use any of its CRDs, so I never gave it any thought. Now I must, even though I don't directly use them. The user experience suffers, but so does the experience for you the developer, and I get that. I'm sorry you need to deal with it! Future readers, this is a good document outlining the helm challenges. |
Confirmed: manually upgrading the CRDs allowed the helm upgrade to v1.1.0 to succeed. Thanks again! |
Describe the bug
Pods never pass health checks, and logs are filled with errors.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Deployment should succeed.
Your environment
Additional context
The text was updated successfully, but these errors were encountered: