Apply a patch release
A patch release fixes issues in a minor version of Sekoia Self-Hosted, for example 1.0.2 for 1.0. To apply it to an installed platform, you extract its archive, load its self-hosted-controller (SHC), set the new release in config.yml, and run Install.
This procedure applies to every patch release of 1.0, from any earlier patch release of 1.0. A patch release adds no feature, configuration key, or CLI command: your config.yml stays valid, and the procedures of this documentation stay the same. The release notes list the fixes and the updated components of each patch release.
Plan a maintenance window: Install restarts K3s
Install runs every stage of the installation again. It restarts the K3s service on the nodes where the K3s files changed, restarts the secret operator of the platform, and redeploys the components updated by the patch release. See Apply a configuration change.
Prerequisites
- The platform is installed and healthy:
exec DiagnosticreportsOKfor every check. Fix the current issues first, so that a failure of the run has one cause. - You have the credentials of the Sekoia release bucket, as for the initial download.
- The orchestration node has 220 GB of free disk space for the new archive and its extracted files, in addition to the current release. See Orchestration node requirements.
- You run the SHC from the orchestration node, with the execution script and the environment variables described in Deploy the platform.
- No other SHC session is installing or updating the platform. See Interrupted Helm operations.
Apply the patch release
-
Set the patch release to apply, for example:
export SH_VERSION="v1.0.2" -
Download and verify the archive of this release. Follow Step 1: Download and verify the release archive of the deployment guide.
-
Transfer the archive to the orchestration node and extract it in the same
$SEKOIA_LOCAL_DIRas the current release. Follow Step 2: Transfer and extract the archive.The new release files land in
$SEKOIA_LOCAL_DIR/platform/$SH_VERSION/, next to the files of the current release. The extraction also adds the security content bundles of the archive to$SEKOIA_LOCAL_DIR/data/<TYPE>/and replaces thelatestfiles with the bundles it contains. -
Load the SHC image of the new release and tag it
v1.0. Follow Step 3: Load the self-hosted-controller (SHC) Docker image.Load the new SHC before you run Install
Each SHC only accepts the releases it supports. The SHC of an earlier patch release rejects the new release with an
UnsupportedReleaseError.The
v1.0tag moves to the new image, so the execution scriptrun-shc.shstays unchanged. To confirm, rundocker images sekoialab/self-hosted-controller-cli: thev1.0tag has the same image ID as the image that you loaded. -
In
config.yml, setglobal.version.platform.versionto the new release:global: version: platform: version: "v1.0.2" -
Start the SHC so that it reads the new value, then validate the configuration:
exec CheckLocalConfig config show global.version.platform.versionIn the interactive interface, quit the interface and open it again after you edit
config.yml. In one-shot CLI mode, each./run-shc.sh <command>reads the current file. -
To apply the release, run:
exec InstallThe run has completed when the
Install.start terminatedmessage reportssuccess=True. In air-gapped mode,DownloadReleaseFilesuses the extracted files of the new release. In online mode, it downloads them from the Sekoia release bucket. The run also publishes and applies the detection rules and intake formats bundles named in the locallatestfiles. -
If a module fails, fix the cause reported in the log, then run
exec Installagain. Nothing is rolled back, and the next run applies only the differences that remain. See Resume after a failure. -
To check the platform, run:
exec DebugArgoCD exec DiagnosticEvery ArgoCD application reports
Sync: SyncedandHealth: Healthy. Every diagnostic check reportsOK.Progressingis normal for a few minutes after the run.
Result
The platform runs the new patch release. The components listed for this release in the release notes were redeployed, and the platform keeps its data and its configuration.
No automatic rollback
The SHC does not roll back the platform to an earlier release. If the platform does not reach a healthy state after the run, contact Sekoia support.
Related links
- Release notes v1.0: Fixes and updated components of each patch release.
- Deploy the platform: Download, extraction, and SHC image steps that this procedure reuses.
- Apply a configuration change: What a run of
Installrestarts on an installed platform. - The deployment process: Installation execution plan, idempotency, and resume after a failure.
- Run platform diagnostics: Check the platform services after the run.