If agent pod is not installed on master node as default (can be modified to install agent on master node as well but it will be really noisy).
If the pod in question is installed under master node, then we won't be able to read anything from it. They might need to consider installing agent on master as well.
Since Kubernetes 1.6, the concept of Taints and Tolerances was introduced. Now rather than the master being off limits, it's simply tainted. If you add the required tolerance to the pod, it will run.
You can simply add the following to your Daemonset:
spec:tolerations: - key: node-role.kubernetes.io/master effect: NoSchedule