How to Set Patch Sync Filters
Livepatch on-prem enables users to synchronise with the hosted server, and this synchronisation process is configurable.
The primary synchronisation filters are:
- System architecture for limiting patches via architecture
- Flavours for limiting the kernel flavour
- Minimum kernel version, only allowing versions greater than the minimum to be sychronised.
Based on the deployment method, below are various ways of setting sync filters.
Reactive Charm
To check if you are running the reactive charm run juju status and look for the charm channel. Any channel including latest/* e.g. latest/stable is a Reactive charm.
Livepatch’s older reactive charm can be configured as described below.
juju config livepatch \
sync_flavors=generic,lowlatency,aws \
sync_architectures=amd64,s390x \
sync_minimum_kernel_version=5.4.0
Operator Framework charm
As described above, run juju status and look for the charm channel to identify the charm. Any channel including ops1.x/* e.g. ops1.x/stable is a Operator Framework charm.
Livepatch’s newest Operator Framework charm can be configured as described below.
juju config livepatch \
patch-sync.flavors=generic,lowlatency,aws \
patch-sync.architectures=amd64,s390x \
patch-sync.minimum_kernel_version=5.4.0
Snap
The Livepatch Server Snap can be configured as follows
sudo snap set canonical-livepatch-server patch-sync.flavors=generic,lowlatency
sudo snap set canonical-livepatch-server patch-sync.architectures=amd64,s390x
sudo snap set canonical-livepatch-server patch-sync.minimum_kernel_version=6.8.0
Config Explained
The table below explains the format for each config option. The format is identical across all deployment methods.
| Parameter | Description |
|---|---|
flavors |
Comma-separated list of kernel flavors to download patches for. |
architectures |
Comma-separated list of kernel architectures to download patches for. |
minimum_kernel_version |
A minimum kernel version of format “0.0.0” denoting the lowest kernel version to download patches for. |