Release Management

Where This Fits in Karios

Karios is the unified infrastructure platform described in Getting Started. Release Management is the Control Center area used to download, install, monitor, and recover platform release updates on management nodes and target hosts.

Required Access

Use this section only with a role that includes Release Management visibility and install authority for your environment.

Minimum operator checks before starting:

• Release Management is visible in the left navigation

• Download and Install actions are visible on eligible rows

• Activity can be opened for job monitoring

If these controls are missing, request Release Management access from a platform administrator before attempting update work.

Purpose

Use this section for release planning, rollout control, and post-release validation workflows.

When to Use

Use Release Management when you are preparing a platform change, executing a controlled release, or validating release outcomes after deployment.

Scope

This section is reserved for release lifecycle operations and documentation updates related to platform versions and controlled rollout practices.

Release Install Flow

Use this sequence:

Download update -> Install -> Select hosts -> Install Now -> Installation starts -> Monitor Activity -> Installation completed

1. Review Releases and Download Update

When to Use:

Use this when updates are available and you need to prepare a release for installation.

Purpose:

Download an available release package before installation.

Steps:

1. Open Control Center -> Release Management.

2. Stay on the Releases tab.

3. Find a release row with Status: Available.

4. Click Download in the row Actions column.

Releases dashboard showing Available and Downloaded states.

What this screenshot shows:

• Releases tab with summary cards (Total Updates, Available, Downloaded, Installed).

• Release table with row status and Download/Install actions.

What you can do from this screen:

• Download a release that is still in Available state.

• Review release summary and open View notes before installation.

Expected Outcome:

• Selected release is downloaded and becomes ready for install.

If this fails:

• Refresh the releases page and retry Download.

2. Start Install for a Downloaded Release

When to Use:

Use this after the release status is Downloaded.

Purpose:

Open the install workflow for the selected downloaded release.

Steps:

1. In Releases tab, locate the target row with Status: Downloaded.

2. Click Install in the Actions column.

Downloaded release rows with Install actions.

What this screenshot shows:

• Downloaded rows in the release table.

• Install action available per downloaded release.

What you can do from this screen:

• Start install workflow for a downloaded release.

• Review release notes before starting install.

Expected Outcome:

• Install Update dialog opens for host selection.

If this fails:

• Recheck that row status is Downloaded.

• Refresh and retry Install.

3. Select Hosts in Install Update Dialog

When to Use:

Use this immediately after opening Install Update.

Purpose:

Choose the hosts that will receive the selected update.

Steps:

1. Review update details (version and summary) in the dialog.

2. Select target hosts from Management Server and Hosts lists.

3. Optionally use Select all if all listed hosts should be updated.

Install dialog showing host checkboxes before installation.

What this screenshot shows:

• Install Update dialog with selected release details.

• Host selection lists and Select all option.

What you can do from this screen:

• Select one or more target hosts for update rollout.

• Cancel or continue installation based on host selection.

Expected Outcome:

• Selected hosts are marked and ready for installation.

If this fails:

• Close and reopen the install dialog.

• Verify hosts are visible and selectable.

4. Click Install Now

When to Use:

Use this after selecting one or more hosts.

Purpose:

Start release installation on selected hosts.

Steps:

1. Confirm at least one host is selected.

2. Click Install Now.

Install dialog with host selected and Install Now enabled.

What this screenshot shows:

• Host checkbox selection applied.

• Install Now button enabled for selected host count.

What you can do from this screen:

• Confirm final host selection.

• Start installation immediately with Install Now.

Expected Outcome:

• Installation request is submitted.

If this fails:

• Ensure host selection is present.

• Retry Install Now after refreshing the releases page.

5. Confirm Installation Start

When to Use:

Use this immediately after clicking Install Now.

Purpose:

Verify that installation has started successfully.

Steps:

1. Confirm success message in the Install Update modal.

2. Continue to Activity/job tracking.

Installation start confirmation message.

What this screenshot shows:

• Success confirmation modal: Installation started successfully.

• Redirect notice to job tracking.

What you can do from this screen:

• Confirm install initiation was accepted.

• Continue to Activity tracking for job status.

Expected Outcome:

• Message confirms installation started successfully.

If this fails:

• Return to releases table and restart install flow for the target release.

6. Monitor Installation from Activity

When to Use:

Use this after installation starts.

Purpose:

Track update jobs and current job state.

Steps:

1. Open Activity tab in Release Management.

2. Monitor cards (Total Jobs, In Progress, Succeeded, Failed).

3. Open job details from the activity list when needed.

Activity tab for release installation jobs.

What this screenshot shows:

• Activity tab with job-state cards.

• Job table area for in-progress/succeeded/failed install jobs.

What you can do from this screen:

• Track overall release installation progress.

• Open individual job details for host-level status.

Expected Outcome:

• Active and completed jobs are visible from Activity.

If this fails:

• Refresh the page and reopen Activity.

• Check if the install request was submitted successfully.

7. Validate Installation Completed

When to Use:

Use this after job state moves to completion.

Purpose:

Validate final host-level result for the release install job.

Steps:

1. Open the completed job details.

2. Verify host row result and completion timestamps.

3. Confirm job status shows successful completion.

Completed job details with host-level success status.

What this screenshot shows:

• Completed job modal with release version, host count, and timestamps.

• Host-level status marked Success.

What you can do from this screen:

• Validate completion details for the selected host.

• Confirm installation completed status for audit/reference.

Expected Outcome:

• Installation completed.

If this fails:

• Review job logs in the job details window.

• Re-run installation for the required hosts.

8. Rollback and Recovery Guidance

When to Use:

Use this when one or more hosts fail update install, remain inconsistent after install, or require controlled recovery to a known-good release.

Purpose:

Stabilize affected hosts and restore release consistency without expanding impact.

Steps:

1. Open Release Management -> Activity and identify failed/inconsistent hosts.

2. Isolate scope to affected hosts only; do not re-run across all hosts by default.

3. Check whether the last known-good release is still available as a downloaded install target.

4. If available, start install for that known-good release and select only affected hosts.

5. Validate completion from Activity job details and confirm host-level status.

6. If no known-good release is available, stop further rollout and escalate through Karios Support with Activity evidence.

Activity view used to identify failed or inconsistent hosts before recovery.

Rollback uses the same host-selection dialog as forward install. Select only the affected hosts.

Expected Outcome:

• Affected hosts return to a known-good release state and rollout risk is contained.

If this fails:

1. Capture failed job IDs, timestamps, and host names from Activity.

2. Hold additional installations on unaffected hosts.

3. Escalate with collected evidence for assisted recovery.