Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-18898

More accurate integration phase

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Won't Do
    • Icon: Minor Minor
    • None
    • camel-k-1.6.4-GA
    • Camel-K
    • False
    • Hide

      None

      Show
      None
    • False
    • Todo

      When you create multiple integrations at once, the builds inside the camel-k operator are not parallel, but sequential, so only when integration1 is built, the integration2 starts to build.

      For example when I create 3 integrations:

      kamel run Java.java
      kamel run Groovy.groovy
      kamel run Yaml.yaml
      

      their phase isn't correctly reflected in their integration object:

      oc get integration
      NAME     PHASE          KIT                        REPLICAS
      groovy   Building Kit   kit-c9bslv0sjdpst34tsf50   
      java     Building Kit   kit-c9bslugsjdpst34tsf4g   
      yaml     Building Kit   kit-c9bsm00sjdpst34tsf5g 
      

      All the integrations are in the phase Building Kit, but only one is actually being built, the others are waiting for their turn.

      Would it make sense to have the default state Pending and only when the operator starts the build process set the state to Building Kit? For example:

      oc get integration
      NAME     PHASE          KIT                        REPLICAS
      groovy   Pending        kit-c9bslv0sjdpst34tsf50   
      java     Building Kit   kit-c9bslugsjdpst34tsf4g   
      yaml     Pending        kit-c9bsm00sjdpst34tsf5g 
      

              Unassigned Unassigned
              avano@redhat.com Andrej Vano
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: