Cilium bug with multi-nodes NSM cluster.

[isZams]

Expected Behavior

Hi everyone.
I would like to deploy a cluster with 4 nodes (1 control-plane and 3 workers) configured to use Cilium. However, when i'm going to use deploy NSM resources spire resources are in "CrashLoopBack" state and then, other resources(like the admission webhook or nsmgr) do not reach a running state.
For what concern Cilium i'm using the guide provided by the website.

I noticed that this problem with the NSM resources is present only when i deploy a cluster with different nodes because, using a single node, everything is fine.

I'm currently using the last stable version of NSM 1.3 (i tried also with 1.2).
I'm using K8s locally on my computer and i'm creating the cluster with Kind.

Do you have any idea about the possible reasons of this problem?
Thanks for your attention and your time.