astefanutti commented on pull request #2292:
URL: https://github.com/apache/camel-k/pull/2292#issuecomment-864876677


   > > I would suggest to research relying on the Pods controller status
   > 
   > When pods are in error state, looking at Deployment object in the 
status.conditions, the type "Available" is False. When pod is running ok, the 
Available state is "True". I think this is a good indicator to reconcilie the 
integration status, this way there is no need to inspect pod status anymore, 
WDYT ?
   
   I agree, it may be needed also to rely on the `appsv1.DeploymentProgressing` 
condition, and check it equals to `NewReplicaSetAvailable`, in order to cover 
the use case where the latest ReplicaSet failed, the Deployment controller 
rolls back to the previous ReplicaSet that succeeds, but does not correspond to 
the latest version of the Integration.
   
   Once we're good for Deployment, we also have to handle the cases where the 
Integration is deployed as a KnativeService, or a CronJob, using the specific 
conditions that these other resources expose.


-- 
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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to