Investigate always adding a no-execute taint on kubernetes on start

We have a case where if a pod is consuming locked host paths, on k8s start, it will still try to start but then we add a taint and stop such workloads but the brief window, it's possible the pod started and created empty directories on those paths which is not acceptable.

We should investigate if we can start k3s with some taints already added so that no pods start executing automatically and we can workaround this case then.