Race with multus daemonset when autoscaling

This approach described here with lamda that assigns extra ENI and the "Automated Multus pod IP management" init container works well for me in order to get extra interface in pod with multus. In my setup primary pod interface is still managed by aws-vpc-cni.

My only issue is that when adding more instances (due to cluster-autoscaler) is that sometimes my workload gets started before the multus dameonset has finished running. When this happens only the `/etc/cni/net.d/10-aws.conflist` exists and not the `/etc/cni/net.d/00-multus.conf` causing pod to start without extra interfaces and the "Automated Multus pod IP management" container gets stuck forever.

Is there any known fix for this?