{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #4: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #5: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #6: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #7: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #8: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #9: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #10: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #11: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #12: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #13: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #14: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #15: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:47: 🔍 Diagnostic information for deployment cleanup-ibmcloud-1758893543-workload:
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-45q7m
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-ljm69
    waiting.go:203: Check #16: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #17: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #18: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #19: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #20: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:47: 🔍 Diagnostic information for deployment cleanup-ibmcloud-1758893543-workload:
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-45q7m
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-ljm69
    waiting.go:203: Check #21: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #22: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #23: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #24: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #25: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:47: 🔍 Diagnostic information for deployment cleanup-ibmcloud-1758893543-workload:
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-45q7m
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-ljm69
    waiting.go:203: Check #26: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #27: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #28: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #29: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #30: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:47: 🔍 Diagnostic information for deployment cleanup-ibmcloud-1758893543-workload:
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-45q7m
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-ljm69
    waiting.go:203: Check #31: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #32: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #33: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #34: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #35: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:47: 🔍 Diagnostic information for deployment cleanup-ibmcloud-1758893543-workload:
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-45q7m
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-8qpxq
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-ljm69
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-s9f6j
    waiting.go:203: Check #36: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #37: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #38: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #39: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #40: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:47: 🔍 Diagnostic information for deployment cleanup-ibmcloud-1758893543-workload:
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-45q7m
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-8qpxq
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-ljm69
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-s9f6j
    waiting.go:203: Check #41: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #42: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #43: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #44: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #45: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:47: 🔍 Diagnostic information for deployment cleanup-ibmcloud-1758893543-workload:
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-45q7m
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-8qpxq
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-ljm69
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-s9f6j
    waiting.go:203: Check #46: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #47: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #48: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #49: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #50: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:47: 🔍 Diagnostic information for deployment cleanup-ibmcloud-1758893543-workload:
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-45q7m
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-8qpxq
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-ljm69
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-s9f6j
    waiting.go:203: Check #51: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #52: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #53: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #54: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #55: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:47: 🔍 Diagnostic information for deployment cleanup-ibmcloud-1758893543-workload:
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-45q7m
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-8qpxq
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-ljm69
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-s9f6j
    waiting.go:203: Check #56: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #57: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #58: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #59: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #60: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:47: 🔍 Diagnostic information for deployment cleanup-ibmcloud-1758893543-workload:
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-45q7m
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-8qpxq
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-ljm69
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-s9f6j
    waiting.go:203: Check #61: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #62: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #63: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #64: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #65: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:47: 🔍 Diagnostic information for deployment cleanup-ibmcloud-1758893543-workload:
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-45q7m
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-8qpxq
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-667p6
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-ljm69
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-s9f6j
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-lkkzj
    waiting.go:203: Check #66: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #67: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #68: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #69: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #70: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:47: 🔍 Diagnostic information for deployment cleanup-ibmcloud-1758893543-workload:
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-45q7m
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-8qpxq
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-667p6
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-ljm69
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-s9f6j
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-lkkzj
    waiting.go:203: Check #71: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #72: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #73: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #74: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #75: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:47: 🔍 Diagnostic information for deployment cleanup-ibmcloud-1758893543-workload:
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-45q7m
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-8qpxq
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-667p6
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-ljm69
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-s9f6j
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-lkkzj
    waiting.go:203: Check #76: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #77: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #78: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #79: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #80: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:47: 🔍 Diagnostic information for deployment cleanup-ibmcloud-1758893543-workload:
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-45q7m
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-8qpxq
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-667p6
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-ljm69
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-s9f6j
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-lkkzj
    waiting.go:203: Check #81: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #82: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #83: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #84: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #85: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:47: 🔍 Diagnostic information for deployment cleanup-ibmcloud-1758893543-workload:
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-45q7m
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-8qpxq
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-667p6
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-ljm69
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-s9f6j
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-lkkzj
    waiting.go:203: Check #86: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #87: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    waiting.go:203: Check #88: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #89: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    waiting.go:203: Check #90: Deployment cleanup-ibmcloud-1758893543-workload: 0/2 replicas ready, 0 available, 2 unavailable
    diagnostics.go:355: 📊 NodeClaims in cluster: 2
    diagnostics.go:328: 📊 NodePool cleanup-ibmcloud-1758893543-nodepool status:
    diagnostics.go:329:   Conditions:
    diagnostics.go:331:     - Type: NodeClassReady, Status: True, Reason: NodeClassReady, Message: 
    diagnostics.go:331:     - Type: NodeRegistrationHealthy, Status: Unknown, Reason: AwaitingReconciliation, Message: object is awaiting reconciliation
    diagnostics.go:331:     - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 
    diagnostics.go:331:     - Type: Ready, Status: True, Reason: Ready, Message: 
    diagnostics.go:336:   Resources:
    diagnostics.go:338:     - CPU: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:339:     - Memory: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:340:     - Pods: {{0 0} {<nil>} 0 DecimalSI}
    diagnostics.go:47: 🔍 Diagnostic information for deployment cleanup-ibmcloud-1758893543-workload:
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-45q7m
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-8qpxq
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qmrg4 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-667p6
    diagnostics.go:50: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 status: Phase=Pending, Reason=
    diagnostics.go:55: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 condition PodScheduled: False - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: FailedScheduling - 0/2 nodes are available: 1 node(s) had untolerated taint {evict-test: true}, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-ljm69
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-s9f6j
    diagnostics.go:72: Pod cleanup-ibmcloud-1758893543-workload-6f4cbb9b4b-qrgg5 event: Nominated - Pod should schedule on: nodeclaim/cleanup-ibmcloud-1758893543-nodepool-lkkzj
    waiting.go:225: 
        	Error Trace:	/__w/karpenter-provider-ibm-cloud/karpenter-provider-ibm-cloud/test/e2e/waiting.go:225
        	            				/__w/karpenter-provider-ibm-cloud/karpenter-provider-ibm-cloud/test/e2e/cleanup_test.go:263
        	Error:      	Received unexpected error:
        	            	Get "https://kubernetes.default.svc.cluster.local:443/apis/apps/v1/namespaces/default/deployments/cleanup-ibmcloud-1758893543-workload": context deadline exceeded
        	Test:       	TestE2ECleanupIBMCloudResources
        	Messages:   	Deployment pods should be scheduled and running within timeout
--- FAIL: TestE2ECleanupIBMCloudResources (934.28s)
FAIL
FAIL	github.com/pfeifferj/karpenter-provider-ibm-cloud/test/e2e	934.312s
FAIL
