Pods from a DaemonSet cannot be scheduled into any node in OpenShift

Issue

• The Pods from a DaemonSet are in Pending state.

• The message in the Pods shows that 1 node(s) didn''t have free ports for the requested pod ports, and other nodes didn''t match Pod''s node affinity/selector:

        message: '0/22 nodes are available: 1 node(s) didn''t have free ports for the
      requested pod ports, 15 node(s) didn''t match Pod''s node affinity/selector,
      3 node(s) had taint {node-role.kubernetes.io/infra: }, that the pod didn''t
      tolerate, 3 node(s) had taint {node-role.kubernetes.io/master: }, that the
      pod didn''t tolerate.'
  

• The instana-agent Pods are in Pending state with above message. Changing the hostPort used by the instana-agent the Pods are able to start, but those ports can not be changed as per the Instana documentation and changing them don't show any information collected in the Instana SaaS website.

• The following message is shown in the events of the namespace:

  15m16s        Warning   FailedScheduling   pod/[pod_name]   0/22 nodes are available: 1 node(s) didn't have free ports for the requested pod ports, 15 node(s) didn't match Pod's node affinity/selector, 3 node(s) had taint {node-role.kubernetes.io/infra: }, that the pod didn't tolerate, 3 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate