Paul Czarkowski <pczarkowski@...>
Both are completely valid option. People generally like the rollback commands as it's rolling your kubernetes manifests back to a known good version, therefore if there was an error introduced by a change in the Helm charts themselves it would not continue that error.
However this option doesn't take into account the application itself. If there is a bug in the application or you have a backwards incompatible database schema change, then it would make sense to roll forward with a newer image and a `helm upgrade`.
From: cncf-helm@... <cncf-helm@...> on behalf of vtejaswini1@... <vtejaswini1@...>
Sent: Wednesday, July 1, 2020 8:35 AM
To: cncf-helm@... <cncf-helm@...>
Subject: [cncf-helm] What is the proper way to rollback using helm, Is it using "helm rollback" or "helm upgrade olderversion"?
I was looking at downgrading software on failure. I wonder if I need to run upgrade an older version or use the "helm rollback" command.
Well, I don't have enough arguments about why I need to use "helm rollback" for rolling back software.
Does anyone know the reasons behind this support?