starlingx/docs
Code Issues Proposed changes
Files
c153b65ab35ddc01a55b419da1d2de8eb72f0a88
docs/doc/source/updates/kubernetes/in-service-versus-reboot-required-software-updates.rst
Ron Stone dd8efe5f85 Upgrades edits (r6,r7,dsR6,dsR7) 
Copy edits for typos, markup and other technical issues.
Fix case typo
Fix merge conflicts.
Resolve FixMe issues.
Minor copy edit updates.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: I7d710d3faa957c1cb66cc18c9a248a567e7c580f
2022-10-27 06:34:33 -04:00

1.2 KiB
Raw Blame History

In-Service Versus Reboot-Required Software Updates

In-Service (Reboot-not-Required) and a Reboot-Required software updates are available depending on the nature of the update to be performed.

In-Service software updates provide a mechanism to issue updates that do not require a reboot, allowing the update to be installed on in-service nodes and restarting affected processes as needed.

Depending on the area of software being updated and the type of software change, installation of the update may or may not require the hosts to be rebooted. For example, a software update to the kernel would require the host to be rebooted in order to apply the update. Software updates are classified as reboot-required or reboot-not-required (also referred to as in-service) type updates to indicate this. For reboot-required updates, the hosted application pods are automatically relocated to an alternate host as part of the update procedure, prior to applying the update and rebooting the host.