get ds gives you current status of the DaemonSet, but to see why its Pods (or rather, container(s) in these pods) aren't running you'll have to describe the pods, not the DaemonSet.

1. Run kubectl get pods -n testing to get a list of pods. Since this is a DaemonSet, there should be one pod per worker node. The STATUS column tells you which state the pod is currently in. Ideally it should say Running.
2. If STATUS is not Running, grab the pod NAME and run kubectl describe pod <pod_name> -n testing. Look for the Events section towards the bottom; It normally tells you what's wrong with your pod.
3. If the log says it's trying to restart a failed container, that means the service itself is most likely crashing. You can check the logs from the service by running kubectl logs <pod_name> -n testing.

This is typically enough to troubleshoot service-related issues preventing pods from starting up. If you still cannot figure out what the problem is, please update your question with output from each of these steps (after omitting personal/sensitive information, of course) so we can help you further.