Followup, on canonical-livepatch-server latest/edge rev 30 (charm) and canonical-livepatch-server-admin latest/candidate rev 15 (snap) (requires schema-upgrade on the server), the new supported-kernels feature looks like it can be used to narrow down which kernels are in scope.
The list starts populated, and unfortunately the admin tool does not accept wildcards, but you can trim the list with:
canonical-livepatch-server-admin supported-kernels remove "4.4" amd64 gcp xenial
I wrote a script with three nested for/in loops to remove the excess and now "livepatch-admin supported-kernels list" returns precisely the one kernel that I am using.
This feature does not seem to reach charm config, where it might be expected to be found alongside the earlier sync_flavors setting.
However, running livepatch-admin sync trigger just goes and downloads 5546 of them anyway, so it seems likely that I just do not understand this feature.
Followup, on canonical- livepatch- server latest/edge rev 30 (charm) and canonical- livepatch- server- admin latest/candidate rev 15 (snap) (requires schema-upgrade on the server), the new supported-kernels feature looks like it can be used to narrow down which kernels are in scope. livepatch- server- admin supported-kernels remove "4.4" amd64 gcp xenial
The list starts populated, and unfortunately the admin tool does not accept wildcards, but you can trim the list with:
canonical-
I wrote a script with three nested for/in loops to remove the excess and now "livepatch-admin supported-kernels list" returns precisely the one kernel that I am using.
This feature does not seem to reach charm config, where it might be expected to be found alongside the earlier sync_flavors setting.
However, running livepatch-admin sync trigger just goes and downloads 5546 of them anyway, so it seems likely that I just do not understand this feature.