tdiesler opened a new issue, #5623:
URL: https://github.com/apache/camel-k/issues/5623

   ### What happened?
   
   The resource is there and reported Running/Ready
   However, the following wait blocks until timeout
   
   ```
   $ kamel get -n $YAKS_NAMESPACE                            
   NAME                 PHASE   KIT
   logger-sink-pipe     Running default/kit-cpknev3qs4ds73bmkimg
   timer-source-pipe    Running default/kit-cpknev3qs4ds73bmkin0
   
   $ kubectl get pipe logger-sink-pipe -n $YAKS_NAMESPACE    
   NAME               PHASE   REPLICAS
   logger-sink-pipe   Ready   1
   
   $ kubectl wait pipe logger-sink-pipe --for=condition=Ready --timeout=3m -n 
$YAKS_NAMESPACE
   ... times out
   ```
   
   I would expect kubectl wait to return immediately.
   
   On further inspection I see ...
   
   ```
   $ kubectl get pipe logger-sink-pipe -n $YAKS_NAMESPACE -o yaml
   apiVersion: camel.apache.org/v1
   kind: Pipe
   ...
   status:
     conditions:
     - lastTransitionTime: "2024-06-12T11:00:30Z"
       lastUpdateTime: "2024-06-12T11:00:30Z"
       message: Configuration "logger-sink-pipe" is waiting for a Revision to 
become
         ready.
       reason: RevisionMissing
       status: "False"
       type: Ready
     observedGeneration: 1
     phase: Ready
     replicas: 1
     selector: camel.apache.org/integration=logger-sink-pipe
   ```
   
   The Revision seems to be there ...
   
   ```
   $ kubectl get revisions -n $YAKS_NAMESPACE        
   NAME                     CONFIG NAME        K8S SERVICE NAME   GENERATION   
READY   REASON   ACTUAL REPLICAS   DESIRED REPLICAS
   logger-sink-pipe-00001   logger-sink-pipe                      1            
True             1                 1
   ```
   
   ### Steps to reproduce
   
   _No response_
   
   ### Relevant log output
   
   _No response_
   
   ### Camel K version
   
   _No response_


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

Reply via email to