by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Gheorghe-Teodor Bercea
    @doru1004
    When I do a kamel uninstall and then an install again, is there any reuse happening ?
    It always seems like the second install is faster than the first, if so is there some cache I need to clear?
    Also when I do kamel run on an integration I'd like the builder to run every time for debug purposes, not sure what I need to modify to get that effect
    Luca Burgazzoli
    @lburgazzoli
    if you are changing the go code, then you need to build a container image, push to a registry and reference it upon install
    Gheorghe-Teodor Bercea
    @doru1004
    I'm doing that
    Luca Burgazzoli
    @lburgazzoli
    so delete the kits
    and the builder will kick in
    Gheorghe-Teodor Bercea
    @doru1004
    how do I clear the kits?
    Luca Burgazzoli
    @lburgazzoli
    kamel delete kit
    or with kubectl
    Gheorghe-Teodor Bercea
    @doru1004
    is there an additional option I need to pass kamel install with the new image path? I only do this: kamel install --registry=registry:5000 --registry-insecure
    Gheorghe-Teodor Bercea
    @doru1004
    $ k get pods
    NAME READY STATUS RESTARTS AGE
    camel-k-kit-bs49lrom5h99pjsjpdig-builder 0/1 Completed 0 14d
    camel-k-operator-68c8fcf59b-fll45 1/1 Running 0 34m
    That's all I have
    This is what is outputted when I run kamel run:
    integration "sink" created
    Condition "IntegrationPlatformAvailable" is "True" for Integration sink: camel-k
    Progress: integration "sink" in phase Initialization
    Integration sink in phase "Initialization"
    Progress: integration "sink" in phase Building Kit
    Integration sink in phase "Building Kit"
    Condition "IntegrationKitAvailable" is "False" for Integration sink: creating a new integration kit
    Progress: integration "sink" in phase Deploying
    Condition "IntegrationKitAvailable" is "True" for Integration sink: kit-bs49lrom5h99pjsjpdig
    Integration sink in phase "Deploying"
    Progress: integration "sink" in phase Running
    Condition "DeploymentAvailable" is "True" for Integration sink: deployment name is sink
    Condition "CronJobAvailable" is "False" for Integration sink: different controller strategy used (deployment)
    Condition "ServiceAvailable" is "False" for Integration sink: no http service required
    Condition "ExposureAvailable" is "False" for Integration sink: no host or service defined
    Integration sink in phase "Running"
    Condition "Ready" is "False" for Integration sink
    Condition "Ready" is "True" for Integration sink
    Then it just runs and no builder gets invoked
    Luca Burgazzoli
    @lburgazzoli
    if it runs without build it means a compatible kit is still there
    kubectl delete ik —all
    Gheorghe-Teodor Bercea
    @doru1004
    That worked
    Nice, I can even see it now inside the local registry if I use k get ik
    Thanks a lot!
    Gheorghe-Teodor Bercea
    @doru1004
    Is there an additional parameter I need to give kamel install to force it to pull the image from docker or does it do that by default ?
    Gheorghe-Teodor Bercea
    @doru1004
    I changed the builder go code and I want to print some debug messages, where are those messages printed? I use fmt with os.Stdout and I also used log.info () but I can't find where those output messages get printed
    Luca Burgazzoli
    @lburgazzoli
    you can run the operator outside the cluster
    6 replies
    so scale the deployment
    set the env var WATCH_NAMESPACE to the namespace
    and run
    kamel operator
    Gheorghe-Teodor Bercea
    @doru1004
    Is there a way to force kamel to update the operator?
    Pull the image again from docker etc
    I can currently achieve this by deleting my cluster and starting again which is slow and time consuming. (kamel uninstall, followed by a kamel install doesn't trigger an image pull from docker)
    Stefan Bergstein
    @stefan-bergstein

    I am trying to use aws-s3 with an on-premise S3 store. It look like the cert of the CA is missing:

    Caused by: com.amazonaws.SdkClientException: Unable to execute HTTP request: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

    Is there an example for adding the required certificate into the camel integration?

    Anton
    @anton-goncharov_gitlab
    Can anyone please clarify, as the Groovy DSL has been deprecated in Camel since 2.19, is there any recommendation about using it with Camel K? I see Groovy among the languages in the Camel K documentation without any relevant notice. So will it be supported despite the fact it's discontinued in Camel?
    Andrea Cosentino
    @oscerd
    The Groovy language has been removed from the main camel project
    it will be supported as language only in camel-k
    alongside other languages
    like kotlin
    js
    etc.
    mykola.zerniuk
    @kolunyaa
    Hi guys! I am trying to make HTTPS request using PEM certificate file which contains both private key and certification. It works using curl like (curl -E ./commonapi.pem) but i didn't find working solution using Kamel K. The option from documentation with Jolokia trait (https://camel.apache.org/camel-k/latest/traits/jolokia.html) fails when i set jolokia.ca-cert with file path on local machine where i run integration.
    Could not start Jolokia agent: java.lang.IllegalStateException: Cannot open keystore for https communication: java.io.FileNotFoundException: No such CA cert
    Seems like it doesn't look in local fs. Probably someone knows where to put my certificate file to make this option work or some different approach.
    Ricardo M. Augusto
    @rmaugusto
    Hello guys, I installed camel-k in my cluster with AWS EKS using helm (operator 1.1.0), when I install an integration with "kamel run test.groovy" it seems camel-k is stucked, no kit is installed and no error log in operator pod.
    image.png
    If I try exactly the same with minikube it works.
    Ricardo M. Augusto
    @rmaugusto
    Is anybody running camel-k on AWS+EKS ?
    Nicola Ferraro
    @nicolaferraro
    Hi, @rmaugusto, I guess installing Camel K on AWS+EKS has always been the hardest one.. Did you try to setup a registry for images after installing?
    Ricardo M. Augusto
    @rmaugusto

    Hi, @rmaugusto, I guess installing Camel K on AWS+EKS has always been the hardest one.. Did you try to setup a registry for images after installing?

    I saw ECR is not supported yet, I installed registry over proxy for ECR ( https://hub.docker.com/r/catalinpan/aws-ecr-proxy/ )... I have tried some docker commands and worked, I'm gonna try new registry. How could I debug ? I could not see any error log.

    4 replies
    Ricardo M. Augusto
    @rmaugusto
    Server Version: version.Info{Major:"1", Minor:"16+", GitVersion:"v1.16.8-eks-fd1ea7", GitCommit:"fd1ea7c64d0e3ccbf04b124431c659f65330562a", GitTreeState:"clean", BuildDate:"2020-05-28T19:06:00Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}