You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had today a situation where a helm deployment had such history:
Revision 1 - status deployed
Revision 2 - status failed
Revision 3 - status failed
I run helm mapkubeapis NAME_OF_RELEASE and it showed that there were no changes needed.
Then I run helm upgrade --install and it faield that PDB has version policy/v1beta1.
It seems that helm tries to upgrade from last successful revision, but helm-mapkubeapis takes into account only last one.
As a workaround I deleted form kubernetes secrets of helm releases that are failed and run helm mapkubeapis NAME_OF_RELEASE
The text was updated successfully, but these errors were encountered:
I had today a situation where a helm deployment had such history:
Revision 1 - status deployed
Revision 2 - status failed
Revision 3 - status failed
I run
helm mapkubeapis NAME_OF_RELEASE
and it showed that there were no changes needed.Then I run
helm upgrade --install
and it faield that PDB has version policy/v1beta1.It seems that helm tries to upgrade from last successful revision, but helm-mapkubeapis takes into account only last one.
As a workaround I deleted form kubernetes secrets of helm releases that are failed and run
helm mapkubeapis NAME_OF_RELEASE
The text was updated successfully, but these errors were encountered: