Application users expect 24x7x365 availability. But, developers are expected to deploy updates frequently. Today's tablestakes requirement for applications is to be able to perform updates without affecting application availability.
Workloads based on the "workload wizard" can select the appropriate update strategy suitable for the application.
Rolling Upgrade Strategy¶
Rolling upgrades allow for incremental updates of the container replicas with new ones. This is the default upgrade strategy supported by the platform.
This upgrade option is primarily targeted at developers or QA type workloads where application downtime or availability is not a concern.
With this option, the previous version of the container image that is running is terminated before the new version is started.