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

   Hi,
   
   I have Camel-k 1.12.1 with configuration IntegrationPlatform 
   ```
   apiVersion: camel.apache.org/v1
   kind: IntegrationPlatform
   metadata:
     labels:
       app: camel-k
       app.kubernetes.io/managed-by: Helm
       app.kubernetes.io/name: camel-k
       app.kubernetes.io/version: 1.12.1
       helm.sh/chart: camel-k-1.0.6
     name: camel-k
     namespace: default
   spec:
     build:
       baseImage: 10.22.17.12/openjdk:17.0.1-jdk-slim
       maven:
         settings:
           configMapKeyRef:
             key: settings.xml
             name: maven-settings
       maxRunningBuilds: 8
       registry:
         address: 10.22.17.12
         insecure: true
         organization: psexper
         secret: camel-k-registry-secret
     cluster: kubernetes
   status:
     build:
       PublishStrategyOptions:
         KanikoPersistentVolumeClaim: camel-k
       baseImage: 10.22.17.12/psexper/openjdk:17.0.1-jdk-slim
       buildStrategy: routine
       maven:
         cliOptions:
         - -V
         - --no-transfer-progress
         - -Dstyle.color=never
         localRepository: /tmp/artifacts/m2
         settings:
           configMapKeyRef:
             key: settings.xml
             name: maven-settings
       maxRunningBuilds: 8
       publishStrategy: Spectrum
       registry:
         address: 10.22.17.12
         insecure: true
         organization: psexper
         secret: camel-k-registry-secret
       runtimeVersion: 1.17.1
       timeout: 5m0s
     cluster: kubernetes
     info:
       gitCommit: f2543a9f6269aad3cc24de3061b130c0e7590c09
       goOS: linux
       goVersion: go1.19.4
     kamelet:
       repositories:
       - uri: none
     observedGeneration: 3
     phase: Ready
     version: 1.12.1
   ```
   
   When I run build more integration I see
   
   NAME                       PHASE        AGE   STARTED   DURATION   ATTEMPTS
   kit-cir3vvt8jb0c73ftq95g   Running      36s   36s
   kit-cir40058jb0c73ftq960   Scheduling   36s
   kit-cir408d8jb0c73ftq96g   Scheduling   2s
   kit-cir408l8jb0c73ftq970   Scheduling   2s
   kit-cir408l8jb0c73ftq97g   Scheduling   2s
   kit-cir408l8jb0c73ftq980   Scheduling   2s
   
   Why didn't more builds start at the same time
   


-- 
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-unsubscr...@camel.apache.org.apache.org

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

Reply via email to