lsergio commented on issue #5552: URL: https://github.com/apache/camel-k/issues/5552#issuecomment-2135067559
After reading [this method](https://github.com/apache/camel-k/blob/v2.2.0/pkg/controller/integration/monitor.go#L349), I figured out what is happening: While there's no available nodes, the integration pod status is Pending and it reports: ``` status: conditions: - lastProbeTime: null lastTransitionTime: "2024-05-28T12:00:15Z" message: '0/6 nodes are available: 6 Insufficient cpu. preemption: 0/6 nodes are available: 6 No preemption victims found for incoming pod..' reason: Unschedulable status: "False" type: PodScheduled phase: Pending qosClass: Burstable ``` The monitor detects the Unschedulable reason and sets the Error reason in the Integration. When the new node is ready, that condition changes to: ``` - lastProbeTime: null lastTransitionTime: "2024-05-28T12:01:07Z" status: "True" type: PodScheduled ``` There probably is a good reason for checking the pending Pod statuses, but shouldn't it be enough to check the Deployment status? Any issue with the pods will (or should) reflect on the Deployment status. For my specific monitoring case, I will try and check the Deployment status. If it is still Progressing, I will ignore the Error reason. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
