Comment 3 for bug 1989651

And finally, as brought up in an Azure sync call by Chris, we could also avoid automatic removal of the cached obj.pkl file per boot via /lib/systemd/system/cloud-init-local.service.d/50-azure-clear-persistent-obj-pkl.conf.

Cloud-init 21.4 has already SRU'd functionality to Focal that has capacity to re-write network configuration per EventTypeBOOT (which is where one of the _get_data calls we see in the bug description). The risk of the removal of /lib/systemd/system/cloud-init-local.service.d/50-azure-clear-persistent-obj-pkl.conf from focal images should be limited. We have already done this in Jammy and not received any bugs related to the absence of 50-azure-clear-persistent-obj-pkl.conf.