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
When applying a significant change to the helm values, it is possible for the chart to get into a chicken and egg scenario:
i.e. something in the new helm values changes / adds to a ConfigMap. click-upgrade job that runs fails because the expected value is not yet in the ConfigMap, everything explodes in a ball of fire.
It's probably safer to work around this by making the upgrade job not reference the ConfigMap, etc.?
The text was updated successfully, but these errors were encountered:
When applying a significant change to the helm values, it is possible for the chart to get into a chicken and egg scenario:
i.e. something in the new helm values changes / adds to a ConfigMap. click-upgrade job that runs fails because the expected value is not yet in the ConfigMap, everything explodes in a ball of fire.
It's probably safer to work around this by making the upgrade job not reference the ConfigMap, etc.?
The text was updated successfully, but these errors were encountered: