Comment 27 for bug 1910456

Also, we need to request another extension of the CRD to one week later, to February 10th if no one objects.

Our reason for doing this is that we have actually found that our fix in snapd is not applied immediately to running containers and operators/users will need to restart their containers and snapd should not do this automatically. Instead, affected snaps should be refreshed after snapd has been refreshed, and this can be done by adding a small snippet to the snapcraft.yaml of the affected snaps, depending on whether the snap is strict or classic.

As such, we will need some time to communicate with all affected snap authors and coordinate them to release new versions of their snaps.

The specific change for strict snaps such as the docker snap that are affected is that a new revision should be uploaded to the store and released to the stable risk on all active tracks with no changes except to add this snippet to the snap.yaml (if just repacking the snap) or the snapcraft.yaml (if rebuilding the snap):

assumes: [snapd2.48.3]

This ensures that the snap will be automatically refreshed at the next refresh check after the device has been refreshed to snapd version 2.48.3 (which is the version of snapd which will contain the fix).

For affected classic snaps, the same assumes snippet should be added and additionally, all services which are managing containers, i.e. containerd, etc. should add to their plugs the kubernetes-support interface.