Skip to main content
NetApp Knowledge Base

Trident pods can't be properly scheduled in kubernetes nodes, in a new installation

  1. Last updated
    Jul 30, 2024
  2. Save as PDF
Views:
45
Visibility:
Public
Votes:
0
Category:
trident-openshift
Specialty:
SNAPX
Last Updated:
7/30/2024, 11:36:13 AM

Applies to

  • NetApp Astra Trident
  • RedHat Openshift cluster (OCP) 

Issue

After installing Trident in a kubernetes cluster, the Trident pods do not reach running status and getting issues to be assigned to kubernetes nodes:

Events:

  Type     Reason            Age                    From               Message

  ----     ------            ----                   ----               -------

  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

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.