-
Notifications
You must be signed in to change notification settings - Fork 7.1k
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
Print diffs when upgrade fails for validation reasons #1781
Comments
Looking at the chart, my guess is that the problem is that the deployment manifest is changed on upgrade: So even though it's just a changed timestamp in an annotation, it's causing the deployment object to be sent through the update cycle. (Actually, looks like there may be a few places where the statfulset is changed on upgrade -- mostly timestamp related.) Is there a corresponding issue in the charts repo? |
Ah, thanks. I guess that's causing the issue. Adding the The problem aside, I still think Helm's output could be improved. It just printed the error without telling me that the config map was indeed updated. |
Improving output & logging of commands is something we're continually working on. I think we'll need some sort of way to turn on a more verbose mode for output messages. Is it okay if I close this issue? Or would you like to change it up to add a specific feature request for an output message? |
Maybe one option is to to print out the diff between the new and old in case of any validation error? and also notifying user that although the error message, the configmap has been updated actually. |
I'm currently thinking that the requirement for this one would be:
Adding to the 2.3.0 milestone |
So essentially: https://github.com/databus23/helm-diff/ |
yes, that plugin solves this use case exactly. Closing! |
I'm trying out
incubator/mongodb-replicaset
. It works quite nicely so far. I installed it successfully. I then made changes to the ConfigMap containing themongod.conf
and tried to upgrade the chart. The result was this:The only thing that I changed is the ConfigMap. The docs state that Helm only updates things that have changed since the last release. The ConfigMap was actually updated correctly even though the above error was the only output.
The text was updated successfully, but these errors were encountered: