diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #4: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #5: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #6: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #7: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #8: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #9: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #10: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #11: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #12: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #13: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #14: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #15: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu22-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-gjfgs diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-djvkx diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-wkwbr waiting.go:203: Check #16: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #17: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #18: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #19: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #20: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu22-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-gjfgs diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-djvkx diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-wkwbr waiting.go:203: Check #21: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #22: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #23: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #24: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #25: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu22-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-gjfgs diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-djvkx diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-wkwbr waiting.go:203: Check #26: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #27: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #28: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #29: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #30: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu22-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-gjfgs diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-djvkx diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-wkwbr waiting.go:203: Check #31: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #32: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #33: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #34: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #35: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu22-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-gjfgs diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-m72dc diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-djvkx diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-6d89w diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-wkwbr diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-l7jc7 waiting.go:203: Check #36: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #37: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #38: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #39: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #40: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu22-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-gjfgs diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-m72dc diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-djvkx diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-6d89w diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-wkwbr diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-l7jc7 waiting.go:203: Check #41: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #42: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #43: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #44: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #45: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu22-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-gjfgs diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-m72dc diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-djvkx diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-6d89w diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-wkwbr diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-l7jc7 waiting.go:203: Check #46: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #47: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #48: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #49: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #50: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu22-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-gjfgs diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-m72dc diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-djvkx diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-6d89w diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-wkwbr diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-l7jc7 waiting.go:203: Check #51: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #52: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #53: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #54: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #55: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu22-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-gjfgs diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-m72dc diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-djvkx diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-6d89w diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-wkwbr diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-l7jc7 waiting.go:203: Check #56: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #57: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #58: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #59: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #60: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu22-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-gjfgs diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-m72dc diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-djvkx diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-6d89w diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-wkwbr diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-l7jc7 waiting.go:203: Check #61: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #62: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #63: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #64: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #65: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu22-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-gjfgs diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-m72dc diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-267cr diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-djvkx diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-6d89w diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-cbh6t diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-wkwbr diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-l7jc7 diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-6jfmf waiting.go:203: Check #66: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #67: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #68: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #69: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #70: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu22-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-gjfgs diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-m72dc diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-267cr diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-djvkx diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-6d89w diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-cbh6t diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-wkwbr diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-l7jc7 diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-6jfmf waiting.go:203: Check #71: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #72: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #73: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #74: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #75: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu22-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-gjfgs diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-m72dc diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-267cr diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-djvkx diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-6d89w diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-cbh6t diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-wkwbr diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-l7jc7 diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-6jfmf waiting.go:203: Check #76: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #77: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #78: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #79: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #80: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu22-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-gjfgs diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-m72dc diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-267cr diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-djvkx diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-6d89w diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-cbh6t diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-wkwbr diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-l7jc7 diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-6jfmf waiting.go:203: Check #81: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #82: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #83: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #84: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #85: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu22-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-gjfgs diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-m72dc diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-267cr diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-djvkx diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-6d89w diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-cbh6t diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-wkwbr diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-l7jc7 diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-6jfmf waiting.go:203: Check #86: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #87: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #88: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #89: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #90: Deployment image-selector-test-1758895805-ubuntu22-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 3 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu22-nodepool status: diagnostics.go:329: Conditions: 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: NodeClassReady, Status: True, Reason: NodeClassReady, Message: diagnostics.go:331: - Type: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu22-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck 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 image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-gjfgs diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-m72dc diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c9896wzck event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-267cr diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-djvkx diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-6d89w diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989rs45n event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-cbh6t diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb 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 image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-wkwbr diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-l7jc7 diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu22-workload-587b6c989x62wb event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu22-nodepool-6jfmf 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/image_selector_test.go:67 Error: Received unexpected error: Get "https://kubernetes.default.svc.cluster.local:443/apis/apps/v1/namespaces/default/deployments/image-selector-test-1758895805-ubuntu22-workload": context deadline exceeded Test: TestE2EImageSelector/Ubuntu_22_04_ImageSelector Messages: Deployment pods should be scheduled and running within timeout === RUN TestE2EImageSelector/Ubuntu_24_04_ImageSelector instance_discovery.go:36: Selected instance type for testing: bx2-2x8 image_selector_test.go:236: ✅ Created NodeClass with imageSelector: image-selector-test-1758895805-ubuntu24-nodeclass waiting.go:48: ⏳ Waiting 2s for initial controller processing before validation checks... waiting.go:85: 🔍 NodeClass Spec: VPC=r010-2b1c3cdc-a678-4eda-86af-731130de1c0a, Subnet=02c7-ac2802cf-54bb-4508-aad7-eba7e8c2034c, Zone=eu-de-2, Region=eu-de, InstanceProfile=bx2-2x8 waiting.go:88: 🔍 NodeClass ResourceGroup: 88427352321742ef8cfac50b0ee6cc26 waiting.go:89: 🔍 NodeClass SecurityGroups: [r010-36f045e2-86a1-4af8-917e-b17a41f8abe3] waiting.go:90: 🔍 NodeClass APIServerEndpoint: https://10.243.65.4:6443 waiting.go:91: 🔍 NodeClass ResourceVersion: 26285189 waiting.go:96: Check #1: Controller hasn't processed NodeClass yet (no status conditions), waiting... waiting.go:101: Check #2: NodeClass image-selector-test-1758895805-ubuntu24-nodeclass conditions (ResourceVersion: 26285202): waiting.go:109: ✅ Type: Ready, Status: True, Reason: Ready, Message: NodeClass is ready waiting.go:117: ✅ NodeClass is ready after 2 checks: Ready - NodeClass is ready image_selector_test.go:93: NodeClass with Ubuntu 24.04 imageSelector is ready: image-selector-test-1758895805-ubuntu24-nodeclass instance_discovery.go:62: Selected 3 instance types for testing: [bx2-2x8 cx2-2x4 bx2-4x16] image_selector_test.go:97: Created NodePool: image-selector-test-1758895805-ubuntu24-nodepool image_selector_test.go:101: Created test workload: image-selector-test-1758895805-ubuntu24-workload waiting.go:203: Check #1: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 0 unavailable waiting.go:203: Check #2: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #3: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 6 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu24-nodepool status: diagnostics.go:329: Conditions: diagnostics.go:331: - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 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: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #4: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #5: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #6: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 6 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu24-nodepool status: diagnostics.go:329: Conditions: diagnostics.go:331: - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 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: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #7: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #8: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #9: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 6 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu24-nodepool status: diagnostics.go:329: Conditions: diagnostics.go:331: - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 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: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #10: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #11: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #12: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 6 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu24-nodepool status: diagnostics.go:329: Conditions: diagnostics.go:331: - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 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: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #13: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #14: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #15: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 6 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu24-nodepool status: diagnostics.go:329: Conditions: diagnostics.go:331: - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 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: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu24-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k 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 image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k 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 image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-jtgm9 diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c 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 image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c 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:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 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 image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 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 image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-w9bhl waiting.go:203: Check #16: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #17: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #18: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 6 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu24-nodepool status: diagnostics.go:329: Conditions: diagnostics.go:331: - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 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: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #19: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #20: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu24-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k 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 image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k 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 image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-jtgm9 diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c 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 image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c 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:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 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 image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 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 image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-w9bhl waiting.go:203: Check #21: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 6 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu24-nodepool status: diagnostics.go:329: Conditions: diagnostics.go:331: - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 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: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #22: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #23: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #24: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 6 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu24-nodepool status: diagnostics.go:329: Conditions: diagnostics.go:331: - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 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: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #25: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu24-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k 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 image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k 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 image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-jtgm9 diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c 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 image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c 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:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 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 image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 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 image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-w9bhl waiting.go:203: Check #26: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #27: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 6 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu24-nodepool status: diagnostics.go:329: Conditions: diagnostics.go:331: - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 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: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #28: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #29: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #30: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 6 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu24-nodepool status: diagnostics.go:329: Conditions: diagnostics.go:331: - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 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: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu24-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k 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 image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k 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 image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-jtgm9 diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c 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 image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c 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:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 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 image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 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 image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-w9bhl waiting.go:203: Check #31: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #32: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #33: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 6 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu24-nodepool status: diagnostics.go:329: Conditions: diagnostics.go:331: - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 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: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #34: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #35: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu24-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k 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 image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k 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 image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-jtgm9 diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-nwpqd diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c 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 image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c 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:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 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 image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 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 image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-w9bhl diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-g6bjz waiting.go:203: Check #36: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 6 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu24-nodepool status: diagnostics.go:329: Conditions: diagnostics.go:331: - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 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: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #37: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #38: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #39: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 6 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu24-nodepool status: diagnostics.go:329: Conditions: diagnostics.go:331: - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 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: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #40: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu24-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k 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 image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k 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 image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-jtgm9 diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-nwpqd diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c 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 image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c 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:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 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 image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 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 image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-w9bhl diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-g6bjz waiting.go:203: Check #41: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #42: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 6 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu24-nodepool status: diagnostics.go:329: Conditions: diagnostics.go:331: - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 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: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #43: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #44: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #45: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 6 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu24-nodepool status: diagnostics.go:329: Conditions: diagnostics.go:331: - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 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: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu24-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k 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 image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k 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 image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-jtgm9 diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-nwpqd diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c 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 image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c 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:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 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 image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 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 image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-w9bhl diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-g6bjz waiting.go:203: Check #46: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #47: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #48: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 6 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu24-nodepool status: diagnostics.go:329: Conditions: diagnostics.go:331: - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 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: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #49: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #50: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu24-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k 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 image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k 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 image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-jtgm9 diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-nwpqd diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c 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 image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c 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:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 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 image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 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 image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-w9bhl diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-g6bjz waiting.go:203: Check #51: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 6 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu24-nodepool status: diagnostics.go:329: Conditions: diagnostics.go:331: - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 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: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #52: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #53: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable waiting.go:203: Check #54: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:355: 📊 NodeClaims in cluster: 6 diagnostics.go:328: 📊 NodePool image-selector-test-1758895805-ubuntu24-nodepool status: diagnostics.go:329: Conditions: diagnostics.go:331: - Type: ValidationSucceeded, Status: True, Reason: ValidationSucceeded, Message: 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: Ready, Status: True, Reason: Ready, Message: diagnostics.go:336: Resources: diagnostics.go:338: - CPU: {{0 0} {} 0 DecimalSI} diagnostics.go:339: - Memory: {{0 0} {} 0 DecimalSI} diagnostics.go:340: - Pods: {{0 0} {} 0 DecimalSI} waiting.go:203: Check #55: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable diagnostics.go:47: 🔍 Diagnostic information for deployment image-selector-test-1758895805-ubuntu24-workload: diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k 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 image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k 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 image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-jtgm9 diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu24-workload-867465979d9m4k event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-nwpqd diagnostics.go:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c 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 image-selector-test-1758895805-ubuntu24-workload-867465979fjs2c 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:50: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 status: Phase=Pending, Reason= diagnostics.go:55: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 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 image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 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 image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-w9bhl diagnostics.go:72: Pod image-selector-test-1758895805-ubuntu24-workload-867465979pmhg9 event: Nominated - Pod should schedule on: nodeclaim/image-selector-test-1758895805-ubuntu24-nodepool-g6bjz waiting.go:203: Check #56: Deployment image-selector-test-1758895805-ubuntu24-workload: 0/3 replicas ready, 0 available, 3 unavailable