Re: [I] Improve pipe status when the pod is full of exceptions [camel-k]

["squakez (via GitHub)" <gi...@apache.org>]

squakez commented on issue #4977:
URL: https://github.com/apache/camel-k/issues/4977#issuecomment-1876962139

   I had a look and this is what happening. The `Pipe` creates an `Integration` which finally ends up in spinning up a `Pod`. The `Pod` is tried to restart if it fails for certain reasons:
   ```
   k get pods
   NAME                                  READY   STATUS             RESTARTS      AGE
   aws-s3-source-pipe-7568b69c9b-q9gzx   0/1     CrashLoopBackOff   6 (42s ago)   6m31s
   ```
   So, the Integration, therefore the Pipe, are having a very short period of time, likely a few seconds while the Pod is trying to restart that is in Running state, but eventually turn to the correct error state:
   ```
   $ k get pipe -w
   NAME                 PHASE   REPLICAS
   aws-s3-source-pipe   Error   1
   aws-s3-source-pipe   Ready   1
   aws-s3-source-pipe   Error   1
   aws-s3-source-pipe   Ready   1
   aws-s3-source-pipe   Error   1
   aws-s3-source-pipe   Ready   1
   aws-s3-source-pipe   Error   1
   aws-s3-source-pipe   Ready   1
   aws-s3-source-pipe   Error   1
   ```
   I think this is the expected behavior in the sense that the Integration is running successfully until the Pod crashes. I am not sure if we can change this behavior, and, if that would make sense considering that eventually the Pipe and Integration are correctly set their status. Wdyt @lburgazzoli ?


-- 
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: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org