k0pper commented on issue #3027:
URL: https://github.com/apache/camel-k/issues/3027#issuecomment-1047584034


   I have three integrations running. One KameletBinding, one file created from 
the Karavan Designer and one Java DSL Route.
   
   ```
   (base) prometheus ➤ k get integration bitcoin-telegram --namespace camel-k   
                                                                                
                   
   NAME               PHASE     KIT                        REPLICAS
   bitcoin-telegram   Running   kit-c89ri5s6akgkpi4kjugg   1
   chuck-log          Running   kit-c89q3oc6akgkpi4kjufg   1
   hello              Running   kit-c89ra8c6akgkpi4kjug0   1
   (base) prometheus ➤ k get integration bitcoin-telegram --namespace camel-k   
-o yaml                                                                         
                          
   apiVersion: camel.apache.org/v1
   kind: Integration
   metadata:
     creationTimestamp: "2022-02-21T16:08:55Z"
     generation: 1
     labels:
       camel.apache.org/created.by.kind: KameletBinding
       camel.apache.org/created.by.name: bitcoin-telegram
     name: bitcoin-telegram
     namespace: camel-k
     ownerReferences:
     - apiVersion: camel.apache.org/v1alpha1
       blockOwnerDeletion: true
       controller: true
       kind: KameletBinding
       name: bitcoin-telegram
       uid: 37b6ad84-3e5c-47b7-b269-7058e5d3a709
     resourceVersion: "25399"
     uid: fc8b5027-86b3-4f5b-8c1d-4f96ee5a8afa
   spec:
     configuration:
     - type: property
       value: camel.kamelet.bitcoin-source.source.period = 250
     - type: property
       value: camel.kamelet.telegram-sink.sink.authorizationToken = <AUTH_TOKEN>
     - type: property
       value: camel.kamelet.telegram-sink.sink.chatId = <CHAT_ID>
     flows:
     - route:
         from:
           uri: kamelet:bitcoin-source/source
         id: binding
         steps:
         - to: kamelet:telegram-sink/sink
     profile: Kubernetes
   status:
     conditions:
     - firstTruthyTime: "2022-02-21T16:08:55Z"
       lastTransitionTime: "2022-02-21T16:08:55Z"
       lastUpdateTime: "2022-02-21T16:08:55Z"
       message: camel-k/camel-k
       reason: IntegrationPlatformAvailable
       status: "True"
       type: IntegrationPlatformAvailable
     - firstTruthyTime: "2022-02-21T16:08:55Z"
       lastTransitionTime: "2022-02-21T16:08:55Z"
       lastUpdateTime: "2022-02-21T16:08:55Z"
       message: 'kamelets bitcoin-source,telegram-sink found in repositories: 
(Kubernetes[namespace=camel-k],
         Github[owner=k0pper, repo=custom-kamelets, path=kamelets, ref=])'
       reason: KameletsAvailable
       status: "True"
       type: KameletsAvailable
     - firstTruthyTime: "2022-02-21T16:09:31Z"
       lastTransitionTime: "2022-02-21T16:09:31Z"
       lastUpdateTime: "2022-02-21T16:09:31Z"
       message: kit-c89ri5s6akgkpi4kjugg
       reason: IntegrationKitAvailable
       status: "True"
       type: IntegrationKitAvailable
     - lastTransitionTime: "2022-02-21T16:09:31Z"
       lastUpdateTime: "2022-02-21T16:09:31Z"
       message: different controller strategy used (deployment)
       reason: CronJobNotAvailableReason
       status: "False"
       type: CronJobAvailable
     - firstTruthyTime: "2022-02-21T16:09:31Z"
       lastTransitionTime: "2022-02-21T16:09:31Z"
       lastUpdateTime: "2022-02-21T16:09:31Z"
       message: deployment name is bitcoin-telegram
       reason: DeploymentAvailable
       status: "True"
       type: DeploymentAvailable
     - lastTransitionTime: "2022-02-21T16:09:31Z"
       lastUpdateTime: "2022-02-21T16:09:31Z"
       message: no http service required
       reason: ServiceNotAvailable
       status: "False"
       type: ServiceAvailable
     - firstTruthyTime: "2022-02-21T16:09:31Z"
       lastTransitionTime: "2022-02-21T16:09:31Z"
       lastUpdateTime: "2022-02-21T16:09:31Z"
       message: PodMonitor (bitcoin-telegram) -> integration(8080)
       reason: PrometheusAvailable
       status: "True"
       type: PrometheusAvailable
     - lastTransitionTime: "2022-02-21T16:09:31Z"
       lastUpdateTime: "2022-02-21T16:09:31Z"
       message: no host or service defined
       reason: IngressNotAvailable
       status: "False"
       type: ExposureAvailable
     - firstTruthyTime: "2022-02-21T16:09:33Z"
       lastTransitionTime: "2022-02-21T16:09:33Z"
       lastUpdateTime: "2022-02-21T16:09:33Z"
       message: 1/1 ready replicas
       reason: DeploymentReady
       status: "True"
       type: Ready
     dependencies:
     - camel:core
     - camel:jackson
     - camel:kamelet
     - camel:telegram
     - camel:timer
     - camel:xchange
     - mvn:org.apache.camel.k:camel-k-runtime
     - mvn:org.apache.camel.quarkus:camel-quarkus-microprofile-metrics
     - mvn:org.apache.camel.quarkus:camel-quarkus-yaml-dsl
     digest: veHTupp0iGCVFdSS0Db9DikNq5yTSTLA_p0Kfecm8wL0
     generatedSources:
     - content: |
         - route:
             from:
               uri: kamelet:bitcoin-source/source
             id: binding
             steps:
             - to: kamelet:telegram-sink/sink
       name: camel-k-embedded-flow.yaml
     - contentKey: content
       contentRef: bitcoin-telegram-kamelet-bitcoin-source-template
       language: yaml
       name: bitcoin-source.yaml
     - contentKey: content
       contentRef: bitcoin-telegram-kamelet-telegram-sink-template
       language: yaml
       name: telegram-sink.yaml
     image: 
10.101.121.45/camel-k/camel-k-kit-c89ri5s6akgkpi4kjugg@sha256:2e9eb36378ab5819a756cc20ed38b6a610c6164e845a36a1f0c7ff81e1c54516
     integrationKit:
       name: kit-c89ri5s6akgkpi4kjugg
       namespace: camel-k
     lastInitTimestamp: "2022-02-21T16:08:55Z"
     phase: Running
     platform: camel-k
     profile: Kubernetes
     replicas: 1
     runtimeProvider: quarkus
     runtimeVersion: 1.11.0
     selector: camel.apache.org/integration=bitcoin-telegram
     version: 1.8.0
   ```
   


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