System patching

Apply operating-system patches to a managed cluster's hosts on demand or on a schedule, and track each patch job.

Back to documentation

System patching

Purpose

  • Patch a managed cluster's hosts on demand or on a recurring or one-off schedule.
  • See how many patches are pending on each host and across the cluster.
  • Track patch jobs and their per-step results.
  • Follow live patch progress through the Task Manager.

Prerequisites

  • Root-account-only feature; patching is managed per cluster from the cluster's Manage Patching tab.
  • Minimum permission to view patching: platform.clusters.managed.read
  • Permission to initiate, schedule or cancel patching: platform.clusters.managed.update
  • Full patching management is covered by platform.clusters.managed.*

View patch status and job history

Open the patching tab to see pending patches, the schedule and past jobs.

  1. Open Platform → Clusters (root account only), open a cluster, then select the Manage Patching tab.
  2. Read Current Patch Status: available patch count per host and the total across the cluster.
  3. Review the Patch Schedule card: name, type, next run and last run.
  4. Scan the Patching Job History table: Trigger, Status, Started, Completed and Message.
  5. Expected result: pending patch counts, the active schedule and recent jobs are all visible on one tab.

Patch a cluster now

Trigger an immediate patch run across the cluster.

  1. On the Manage Patching tab, click Patch Now.
  2. The button is disabled while a job is already running, so confirm the cluster is idle first.
  3. Initiating patching creates a patch job that writes directly to the task queue; follow its progress in Task Manager on the top bar.
  4. Expected result: a patch job is created, its Task ID is shown, and the job appears in the Patching Job History.

Schedule recurring or one-off patching

Create or edit a patch schedule for the cluster.

  1. On the Manage Patching tab, click Manage Schedule.
  2. Choose a Schedule Type: Recurring or One-off (the type cannot be changed after creation).
  3. Recurring: set the frequency (daily, weekly, monthly or yearly), the time and days, then a schedule name and optional description.
  4. One-off: pick a future date and time.
  5. Save the schedule.
  6. To remove a schedule, return to the Manage Patching tab, click Delete Schedule and confirm (this cannot be undone).
  7. Expected result: the schedule shows on the Manage Patching tab with its next run time.

Monitor a patch job

Follow a running job's steps to completion.

  1. On the Manage Patching tab, click a job in the Patching Job History.
  2. Review the per-step table: Step, Status, Started, Completed, Duration and Output.
  3. While the job is running or pending, the view refreshes automatically every few seconds.
  4. Follow overall progress in Task Manager on the top bar.
  5. Expected result: each step shows success or failed, with its timing and output.

Best Practices

  • Schedule recurring patching inside a maintenance window rather than during peak hours.
  • Check Current Patch Status before starting a manual patch run.
  • Do not start Patch Now while a scheduled job is already running.
  • Use one-off schedules for planned, dated changes and recurring schedules for routine maintenance.
  • Review a failed step's Output to diagnose patch failures.

Ready to rethink private cloud?

Lower costs. Simplify operations. Deliver more.