Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 1 results
    • https://kb.netapp.com/Cloud/Astra/Trident/Trident_pods_can_t_be_properly_scheduled_in_kubernetes_nodes_in_a_new_installation
      NetApp Astra Trident RedHat Openshift cluster (OCP) After installing Trident in a kubernetes cluster, the Trident pods do not reach running status and getting issues to be assigned to kubernetes nodes...NetApp Astra Trident RedHat Openshift cluster (OCP) After installing Trident in a kubernetes cluster, the Trident pods do not reach running status and getting issues to be assigned to kubernetes nodes: Warning FailedScheduling xmys (x155 over 13h) default-scheduler 0/9 nodes are available: 1 node(s) didn't match Pod's node affinity/selector. preemption: 0/9 nodes are available: 1 Preemption is not helpful for scheduling, 8 node(s) didn't match Pod's node affinity/selector