In the daemonset object, when the customer specifies the selinux profile explicitly using securityContext->seLinuxOptions->type, the profile gets assigned as [expected.]
If the customer removes that part, the customer thought that using a security profile binding would be sufficient in order to have the profile injected automatically (by the mutating webhook the cutsomer assume).
But when the customer checks the pod specs the selinux type is empty and the container context is set to the default container_t.