camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [camel-k] nicolaferraro commented on issue #1206: Knative services are slow to become ready
Date Tue, 11 Feb 2020 15:48:51 GMT
nicolaferraro commented on issue #1206: Knative services are slow to become ready
URL: https://github.com/apache/camel-k/issues/1206#issuecomment-584701736
 
 
   I think I've isolated the issue.
   
   This kservice is fast to start:
   
   ```
   apiVersion: serving.knative.dev/v1
   kind: Service
   metadata:
     labels:
       camel.apache.org/generation: "1"
       camel.apache.org/integration: fast-printer
     name: fast-printer
     namespace: default
   spec:
     template:
       metadata:
         labels:
           camel.apache.org/generation: "1"
           camel.apache.org/integration: fast-printer
       spec:
         containerConcurrency: 0
         containers:
         - args:
           - org.apache.camel.k.main.Application
           command:
           - java
           image: camelk/camel-k-kit-bp1c6ngo4v80887bt9h0:9311
           name: integration
           readinessProbe:
             successThreshold: 1
             tcpSocket:
               port: 0
           workingDir: /deployments
         timeoutSeconds: 300
     traffic:
     - latestRevision: true
       percent: 100
   ```
   
   This one is slow:
   ```
   apiVersion: serving.knative.dev/v1
   kind: Service
   metadata:
     labels:
       camel.apache.org/generation: "1"
       camel.apache.org/integration: fast-printer
     name: fast-printer
     namespace: default
   spec:
     template:
       metadata:
         labels:
           camel.apache.org/generation: "1"
           camel.apache.org/integration: fast-printer
       spec:
         containerConcurrency: 0
         containers:
         - args:
           - org.apache.camel.k.main.Application
           command:
           - java
           image: 10.107.75.139/default/camel-k-kit-bp1c6ngo4v80887bt9h0:9311
           name: integration
           readinessProbe:
             successThreshold: 1
             tcpSocket:
               port: 0
           workingDir: /deployments
         timeoutSeconds: 300
     traffic:
     - latestRevision: true
       percent: 100
   
   ```
   
   The only difference is that (the fast) one uses an image from `docker.io`, while the other
uses the Minikube internal registry `10.107.75.139`.
   The serving controller tries to do something with that registry before starting the ksvc
and remains stale.
   
   My best guess is that the serving controller tries to contact it on https port `443`, but
the service never replies on that port (in fact `curl` reaches a timeout) and the controller
remains waiting forever.
   
   Does this sound familiar to you @markusthoemmes ?

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message