Updating cnSGW-C
The rolling software update is a process of updating or migrating the build from an older to a newer version or updating the patch for the prescribed deployment set of application pods.
Rolling update takes place with zero downtime by incrementally updating the pod instances with the new ones.
Note | The applications must be available when new versions are expected to be deployed with the new build versions or patches. |
Update Scope
The rolling update feature is supported from an older to the newer versions within the same major release.
-
Assumptions: When updating, it is assumed that the following has not been changed between the versions:
-
Features supported in the old and the new versions.
-
Configuration addition, deletion, or modification of the existing CLI behavior.
-
Interface change within the peer or across the pods.
-
-
Recommendations:
-
Configuration changes are not recommended during the update process.
-
All configuration changes should be done after the update process is complete.
-
-
Failure Handling: The system should be downgraded manually to an older healthy build following the downgrade process for:
-
Failure during the process such as crash, and pods deployment failures.
-
Failure after the successful update such as new events or procedures.
-