[jira] [Updated] (CAMEL-21381) camel k8s cannot run spring-boot on openshift
[
https://issues.apache.org/jira/browse/CAMEL-21381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21381:
Fix Version/s: 4.8.2
> camel k8s cannot run spring-boot on openshift
> -
>
> Key: CAMEL-21381
> URL: https://issues.apache.org/jira/browse/CAMEL-21381
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.8.2, 4.9.0
>
>
> {code}
> Exporting application ...
> Generating fresh run data
> Exporting as Spring Boot project to: .camel-jbang-run/timer-log
> Building Kubernetes manifest ...
> Project export successful!
> Deploying to openshift ...
> Run: .camel-jbang-run/timer-log/mvnw --file .camel-jbang-run/timer-log
> package k8s:deploy
> [INFO] Scanning for projects...
> [INFO] Downloading from custom2:
> https://repository.apache.org/content/groups/snapshots/org/codehaus/mojo/maven-metadata.xml
> [INFO] Downloading from custom2:
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloaded from custom2:
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-metadata.xml
> (8.8 kB at 24 kB/s)
> [INFO] Downloading from central:
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
> [INFO] Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> (14 kB at 113 kB/s)
> [INFO] Downloaded from central:
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml (21
> kB at 164 kB/s)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.917 s
> [INFO] Finished at: 2024-10-24T07:52:12+02:00
> [INFO]
>
> [ERROR] No plugin found for prefix 'k8s' in the current project and in the
> plugin groups [org.apache.maven.plugins, org.codehaus.mojo]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21381) camel k8s cannot run spring-boot on openshift
[
https://issues.apache.org/jira/browse/CAMEL-21381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21381:
Affects Version/s: 4.8.0
> camel k8s cannot run spring-boot on openshift
> -
>
> Key: CAMEL-21381
> URL: https://issues.apache.org/jira/browse/CAMEL-21381
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.0
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.8.2, 4.9.0
>
>
> {code}
> Exporting application ...
> Generating fresh run data
> Exporting as Spring Boot project to: .camel-jbang-run/timer-log
> Building Kubernetes manifest ...
> Project export successful!
> Deploying to openshift ...
> Run: .camel-jbang-run/timer-log/mvnw --file .camel-jbang-run/timer-log
> package k8s:deploy
> [INFO] Scanning for projects...
> [INFO] Downloading from custom2:
> https://repository.apache.org/content/groups/snapshots/org/codehaus/mojo/maven-metadata.xml
> [INFO] Downloading from custom2:
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloaded from custom2:
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-metadata.xml
> (8.8 kB at 24 kB/s)
> [INFO] Downloading from central:
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
> [INFO] Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> (14 kB at 113 kB/s)
> [INFO] Downloaded from central:
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml (21
> kB at 164 kB/s)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.917 s
> [INFO] Finished at: 2024-10-24T07:52:12+02:00
> [INFO]
>
> [ERROR] No plugin found for prefix 'k8s' in the current project and in the
> plugin groups [org.apache.maven.plugins, org.codehaus.mojo]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21355) LangChain4j Tools fails with direct LLM response
[ https://issues.apache.org/jira/browse/CAMEL-21355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892403#comment-17892403 ] Bruno Meseguer commented on CAMEL-21355: This is an unorthodox one. Camel initiates a conversation with the LLM, which may or may not decide to call the tools. Not calling the tools is a valid use case, so I wouldn't treat it as an exception scenario. I wonder if we should pair the chat component as producer only and tools as consumer only. > LangChain4j Tools fails with direct LLM response > > > Key: CAMEL-21355 > URL: https://issues.apache.org/jira/browse/CAMEL-21355 > Project: Camel > Issue Type: Bug > Components: camel-langchain4j-tools >Affects Versions: 4.8.0 >Reporter: Bruno Meseguer >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.8.2, 4.9.0 > > > The Tools component is designed to provide functions to the LLM. However the > LLM may decide not to invoke any of the given tools. > In that scenario, the LLM replies directly instead of requesting the > execution of a tool/function. The Camel Tools components seems unable to > handle such use case and throws an exception. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21355) LangChain4j Tools fails with direct LLM response
[ https://issues.apache.org/jira/browse/CAMEL-21355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892510#comment-17892510 ] Otavio Rodolfo Piske commented on CAMEL-21355: -- I get your suggestion, but there is something that is not very clear to me. How do you guys propose determining whether the tool call from the LLM is malformed? > LangChain4j Tools fails with direct LLM response > > > Key: CAMEL-21355 > URL: https://issues.apache.org/jira/browse/CAMEL-21355 > Project: Camel > Issue Type: Bug > Components: camel-langchain4j-tools >Affects Versions: 4.8.0 >Reporter: Bruno Meseguer >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.8.2, 4.9.0 > > > The Tools component is designed to provide functions to the LLM. However the > LLM may decide not to invoke any of the given tools. > In that scenario, the LLM replies directly instead of requesting the > execution of a tool/function. The Camel Tools components seems unable to > handle such use case and throws an exception. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21381) camel k8s cannot run spring-boot on openshift
[
https://issues.apache.org/jira/browse/CAMEL-21381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892714#comment-17892714
]
Claus Ibsen commented on CAMEL-21381:
-
Thomas can you help backport this to 4.8.x
> camel k8s cannot run spring-boot on openshift
> -
>
> Key: CAMEL-21381
> URL: https://issues.apache.org/jira/browse/CAMEL-21381
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.0
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.8.2, 4.9.0
>
>
> {code}
> Exporting application ...
> Generating fresh run data
> Exporting as Spring Boot project to: .camel-jbang-run/timer-log
> Building Kubernetes manifest ...
> Project export successful!
> Deploying to openshift ...
> Run: .camel-jbang-run/timer-log/mvnw --file .camel-jbang-run/timer-log
> package k8s:deploy
> [INFO] Scanning for projects...
> [INFO] Downloading from custom2:
> https://repository.apache.org/content/groups/snapshots/org/codehaus/mojo/maven-metadata.xml
> [INFO] Downloading from custom2:
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloaded from custom2:
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-metadata.xml
> (8.8 kB at 24 kB/s)
> [INFO] Downloading from central:
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
> [INFO] Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> (14 kB at 113 kB/s)
> [INFO] Downloaded from central:
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml (21
> kB at 164 kB/s)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.917 s
> [INFO] Finished at: 2024-10-24T07:52:12+02:00
> [INFO]
>
> [ERROR] No plugin found for prefix 'k8s' in the current project and in the
> plugin groups [org.apache.maven.plugins, org.codehaus.mojo]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21386) camel k8s run --dev does not work on openshift
[
https://issues.apache.org/jira/browse/CAMEL-21386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892783#comment-17892783
]
Thomas Diesler commented on CAMEL-21386:
You can now do ...
https://github.com/tdiesler/camel-cloud-examples
{code}
[camel-cloud-examples]$ make k8s-run RUN_MODE=dev
{code}
or
{code}
[camel-cloud-examples]$ make oce-run RUN_MODE=dev
{code}
for all runtimes
> camel k8s run --dev does not work on openshift
> --
>
> Key: CAMEL-21386
> URL: https://issues.apache.org/jira/browse/CAMEL-21386
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.9.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21355) LangChain4j Tools fails with direct LLM response
[ https://issues.apache.org/jira/browse/CAMEL-21355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892870#comment-17892870 ] Otavio Rodolfo Piske commented on CAMEL-21355: -- Bruno and I had a great discussion today and as a result, I modified the code so that it sets a flag on the header (see the linked PR) to indicate to users if a tool has not been called. This satisfies both my intention to let users have a way to handle this scenario, while also providing a clean way to ignore it for users that don't have that need. The code was merged on 4.9 and I'll backport to 4.8.x next week (so, please, keep the ticket open). > LangChain4j Tools fails with direct LLM response > > > Key: CAMEL-21355 > URL: https://issues.apache.org/jira/browse/CAMEL-21355 > Project: Camel > Issue Type: Bug > Components: camel-langchain4j-tools >Affects Versions: 4.8.0 >Reporter: Bruno Meseguer >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.8.2, 4.9.0 > > > The Tools component is designed to provide functions to the LLM. However the > LLM may decide not to invoke any of the given tools. > In that scenario, the LLM replies directly instead of requesting the > execution of a tool/function. The Camel Tools components seems unable to > handle such use case and throws an exception. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21387) Let's add some default dependencies to camel-opentelemetry-starter
[ https://issues.apache.org/jira/browse/CAMEL-21387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21387: Fix Version/s: 4.9.0 > Let's add some default dependencies to camel-opentelemetry-starter > -- > > Key: CAMEL-21387 > URL: https://issues.apache.org/jira/browse/CAMEL-21387 > Project: Camel > Issue Type: Improvement > Components: camel-spring-boot-starters >Affects Versions: 4.8.0 >Reporter: John Poth >Assignee: John Poth >Priority: Minor > Fix For: 4.9.0 > > > Let's add spring-boot-starter-actuator to camel-opentelemetry-starter (as we > do for camel-micrometer-starter) which will set up the Otel Tracer. Among > other things, this has the added benefit of adding HTTP context propagators > by default which is useful. Let's also add > micrometer-tracing-bridge-otel which is also needed [1]. Thanks ! > [1] https://docs.spring.io/spring-boot/reference/actuator/tracing.html > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21355) LangChain4j Tools fails with direct LLM response
[ https://issues.apache.org/jira/browse/CAMEL-21355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892723#comment-17892723 ] Otavio Rodolfo Piske commented on CAMEL-21355: -- I presume you are talking about, let's say, if the user pass invalid characters to the name of the function? Or is it something different? Can you please, give an example of how we could make that happen with Camel? Considering that we do not get that low level into the client API ... Additionally, it's not just a malformed response that may cause the model to decide not to invoke anything. A model is non-deterministic by design and it may decide not to call a tool even if the request is well-formed. Considering this and letting the user decide what they want to do in the absence is a better compromise IMHO. And, please, I am not arguing for the sake of arguing or because of stubbornness, but I do need an specific and concrete scenario. > LangChain4j Tools fails with direct LLM response > > > Key: CAMEL-21355 > URL: https://issues.apache.org/jira/browse/CAMEL-21355 > Project: Camel > Issue Type: Bug > Components: camel-langchain4j-tools >Affects Versions: 4.8.0 >Reporter: Bruno Meseguer >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.8.2, 4.9.0 > > > The Tools component is designed to provide functions to the LLM. However the > LLM may decide not to invoke any of the given tools. > In that scenario, the LLM replies directly instead of requesting the > execution of a tool/function. The Camel Tools components seems unable to > handle such use case and throws an exception. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21376) UseOriginalAggregationStrategy - null pointer
[
https://issues.apache.org/jira/browse/CAMEL-21376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892809#comment-17892809
]
Grzegorz Rozanski commented on CAMEL-21376:
---
I tested 4.8.1 and got the same error.
I created a PR here:
https://github.com/apache/camel/pull/16093
Thanks Claus!
> UseOriginalAggregationStrategy - null pointer
> -
>
> Key: CAMEL-21376
> URL: https://issues.apache.org/jira/browse/CAMEL-21376
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 4.8.0
>Reporter: Grzegorz Rozanski
>Priority: Minor
> Fix For: 4.8.2, 4.9.0
>
> Attachments: camel-null-pointer.log
>
>
> I found a case when NullPointerException occurs in
> UseOriginalAggregationStrategy's aggregate method.
>
> I have this route configuration:
> {code:java}
> .multicast(AggregationStrategies.useOriginal()).parallelProcessing()
> .to(DIRECT_ROUTE1)
> .to(DIRECT_ROUTE2)
> {code}
>
> and in the DIRECT_ROUTE2 there is:
> {code:java}
>
> .doTry()
> .unmarshal().zipFile()
> {code}
> When the zip file is invalid there's exception handling in
> UseOriginalAggregationStrategy::aggregate method:
>
> {code:java}
> exception = checkCaughtException(oldExchange, newExchange);
> if (exception != null) {
> if (original != null) {
> original.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> } else {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> //NULL POINTER oldExchange is null
> }
> } {code}
>
> I checked javadoc about this aggregate method it says that:
> Params:
> oldExchange - the oldest exchange (is null on first aggregation as we only
> have the new exchange)
>
> and I think this is what happens in my case when I get NullPointerException
> in line 78 (oldExchange is null):
>
> {code:java}
> } else {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> }
> {code}
> When I create my own aggregation strategy based on
> UseOriginalAggregationStrategy and modify this `else` part everything works
> properly:
>
> {code:java}
> } else if (oldExchange != null) {
> oldExchange.setProperty(Exchange.EXCEPTION_CAUGHT, exception);
> }
> {code}
>
> I see that similar null check already exists in checkCaughtException method.
>
> The full stack trace can be found as attachment to this ticket.
> This error does not happen on Camel 4.4.0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21385) Camel-Jbang: Spring Boot export with SQL Kamelets requires 'spring.autoconfigure.exclude=org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration' to be f
Andrea Cosentino created CAMEL-21385: Summary: Camel-Jbang: Spring Boot export with SQL Kamelets requires 'spring.autoconfigure.exclude=org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration' to be false Key: CAMEL-21385 URL: https://issues.apache.org/jira/browse/CAMEL-21385 Project: Camel Issue Type: Improvement Components: camel-jbang Reporter: Andrea Cosentino Assignee: Andrea Cosentino This is something useful because otherwise the application will fail, because spring datasource will do autoconfiguration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21384) [camel-micrometer] Analyse the possibility to harmonize the metrics endpoint
[
https://issues.apache.org/jira/browse/CAMEL-21384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pasquale Congiusti updated CAMEL-21384:
---
Description:
I've been testing the Camel-micrometer component with the different runtimes we
have. So far, each of the runtime requires a different set of configuration and
it exposes the metrics in a different endpoint:
{code}
Camel MAIN
(application.properties)
camel.server.enabled=true
camel.server.metricsEnabled=true
camel.metrics.enabled=true
$ camel run test.yaml application.properties
URL --> http://localhost:8080/q/metrics
Camel QUARKUS
Blank application.properties
$ camel run test.yaml --runtime quarkus --dep
mvn:io.quarkus:quarkus-micrometer-registry-prometheus --dep camel-micrometer
URL --> http://localhost:8080/q/metrics
Camel SPRINGBOOT
(application.properties)
management.endpoints.web.exposure.include=prometheus
$ camel run test.yaml application.properties --runtime spring-boot --dep
mvn:io.micrometer:micrometer-registry-prometheus --dep camel-micrometer
URL --> http://localhost:8080/actuator/prometheus
{code}
We should understand if it is feasible to harmonize somehow the configuration
to be able to spit the metrics to the same endpoint OOTB.
was:
I've been testing the Camel-micrometer component with the different runtimes we
have. So far, each of the runtime requires a different set of configuration and
it exposes the metrics in a different endpoint:
{code}
Camel MAIN
(application.properties)
camel.server.enabled=true
camel.server.metricsEnabled=true
camel.metrics.enabled=true
$ camel run test.yaml application.properties
URL --> http://localhost:8080/q/metrics
Camel QUARKUS
Blank application.properties
$ camel run test.yaml --runtime quarkus --dep
mvn:io.quarkus:quarkus-micrometer-registry-prometheus --dep camel-micrometer
URL --> http://localhost:8080/q/metrics
Camel SPRINGBOOT
(application.properties)
management.endpoints.web.exposure.include=prometheus
$ camel run test.yaml application.properties --runtime spring-boot --dep
mvn:io.micrometer:micrometer-registry-prometheus --dep camel-micrometer
URL --> curl http://localhost:8080/actuator/prometheus
{code}
We should understand if it is feasible to harmonize somehow the configuration
to be able to spit the metrics to the same endpoint OOTB.
> [camel-micrometer] Analyse the possibility to harmonize the metrics endpoint
>
>
> Key: CAMEL-21384
> URL: https://issues.apache.org/jira/browse/CAMEL-21384
> Project: Camel
> Issue Type: Improvement
>Affects Versions: 4.x
>Reporter: Pasquale Congiusti
>Assignee: Pasquale Congiusti
>Priority: Minor
>
> I've been testing the Camel-micrometer component with the different runtimes
> we have. So far, each of the runtime requires a different set of
> configuration and it exposes the metrics in a different endpoint:
> {code}
> Camel MAIN
> (application.properties)
> camel.server.enabled=true
> camel.server.metricsEnabled=true
> camel.metrics.enabled=true
> $ camel run test.yaml application.properties
> URL --> http://localhost:8080/q/metrics
> Camel QUARKUS
> Blank application.properties
> $ camel run test.yaml --runtime quarkus --dep
> mvn:io.quarkus:quarkus-micrometer-registry-prometheus --dep camel-micrometer
> URL --> http://localhost:8080/q/metrics
> Camel SPRINGBOOT
> (application.properties)
> management.endpoints.web.exposure.include=prometheus
> $ camel run test.yaml application.properties --runtime spring-boot --dep
> mvn:io.micrometer:micrometer-registry-prometheus --dep camel-micrometer
> URL --> http://localhost:8080/actuator/prometheus
> {code}
> We should understand if it is feasible to harmonize somehow the configuration
> to be able to spit the metrics to the same endpoint OOTB.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21388) Camel Kubernetes plugin Auto Reload with '--dev' option is not working properly
[
https://issues.apache.org/jira/browse/CAMEL-21388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Jelinek updated CAMEL-21388:
Environment: Developer Sandbox for Red Hat OpenShift
> Camel Kubernetes plugin Auto Reload with '--dev' option is not working
> properly
> ---
>
> Key: CAMEL-21388
> URL: https://issues.apache.org/jira/browse/CAMEL-21388
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.1, 4.9.0
> Environment: Developer Sandbox for Red Hat OpenShift
>Reporter: Dominik Jelinek
>Priority: Major
>
> Following docs at
> [https://camel.apache.org/manual/camel-jbang-kubernetes.html#_auto_reload_with_dev_option]
> Consider this command as reproducer
>
> {code:java}
> jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel kubernetes run
> my-route.yaml --cluster-type=openshift --dev {code}
>
> *The '--dev' parameter was working as expected for Camel version 4.8.0 in
> combination with OpenShift cluster* (but it was not working for a deployment
> into eg local Minikube cluster)
> {*}Camel 4.8.1{*}, the '--dev' stopped to work and it is failing with same
> error as when you try with local Minikube (see error below)
>
> {code:java}
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 01:35 min
> [INFO] Finished at: 2024-10-25T12:36:10+02:00
> [INFO]
>
> Run: kubectl get pod -l app.kubernetes.io/name=my-route
> Exception in thread "main" java.util.ServiceConfigurationError:
> io.fabric8.kubernetes.api.model.KubernetesResource:
> io.fabric8.kubernetes.api.model.LimitRange not a subtype
> at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:593)
> at
> java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(ServiceLoader.java:1244)
> at
> java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext(ServiceLoader.java:1273)
> at
> java.base/java.util.ServiceLoader$2.hasNext(ServiceLoader.java:1309)
> at
> java.base/java.util.ServiceLoader$3.hasNext(ServiceLoader.java:1393)
> at java.base/java.util.Iterator.forEachRemaining(Iterator.java:132)
> at
> java.base/java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1939)
> at
> java.base/java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:762)
> at
> java.base/java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:276)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
> at
> java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:179)
> at
> java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:1024)
> at
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)
> at
> java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)
> at
> java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
> at
> java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
> at
> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:596)
> at
> io.fabric8.kubernetes.internal.KubernetesDeserializer$Mapping.registerClassesFromClassLoaders(KubernetesDeserializer.java:215)
> at
> io.fabric8.kubernetes.internal.KubernetesDeserializer.(KubernetesDeserializer.java:90)
> at
> io.fabric8.kubernetes.client.utils.KubernetesSerialization.getKubernetesDeserializer(KubernetesSerialization.java:153)
> at
> io.fabric8.kubernetes.client.utils.KubernetesSerialization.access$000(KubernetesSerialization.java:66)
> at
> io.fabric8.kubernetes.client.utils.KubernetesSerialization$1.deserializerInstance(KubernetesSerialization.java:105)
> at
> com.fasterxml.jackson.databind.deser.DefaultDeserializationContext.deserializerInstance(DefaultDeserializationContext.java:245)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCache.findDeserializerFromAnnotation(DeserializerCache.java:466)
> at
> com.fasterxml.jackson.databind.deser.DeserializerCach
[jira] [Created] (CAMEL-21388) Camel Kubernetes plugin Auto Reload with '--dev' option is not working properly
Dominik Jelinek created CAMEL-21388:
---
Summary: Camel Kubernetes plugin Auto Reload with '--dev' option
is not working properly
Key: CAMEL-21388
URL: https://issues.apache.org/jira/browse/CAMEL-21388
Project: Camel
Issue Type: Bug
Components: camel-jbang
Affects Versions: 4.8.1, 4.9.0
Reporter: Dominik Jelinek
Following docs at
[https://camel.apache.org/manual/camel-jbang-kubernetes.html#_auto_reload_with_dev_option]
Consider this command as reproducer
{code:java}
jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel kubernetes run
my-route.yaml --cluster-type=openshift --dev {code}
*The '--dev' parameter was working as expected for Camel version 4.8.0 in
combination with OpenShift cluster* (but it was not working for a deployment
into eg local Minikube cluster)
{*}Camel 4.8.1{*}, the '--dev' stopped to work and it is failing with same
error as when you try with local Minikube (see error below)
{code:java}
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:35 min
[INFO] Finished at: 2024-10-25T12:36:10+02:00
[INFO]
Run: kubectl get pod -l app.kubernetes.io/name=my-route
Exception in thread "main" java.util.ServiceConfigurationError:
io.fabric8.kubernetes.api.model.KubernetesResource:
io.fabric8.kubernetes.api.model.LimitRange not a subtype
at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:593)
at
java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(ServiceLoader.java:1244)
at
java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext(ServiceLoader.java:1273)
at java.base/java.util.ServiceLoader$2.hasNext(ServiceLoader.java:1309)
at java.base/java.util.ServiceLoader$3.hasNext(ServiceLoader.java:1393)
at java.base/java.util.Iterator.forEachRemaining(Iterator.java:132)
at
java.base/java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1939)
at
java.base/java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:762)
at
java.base/java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:276)
at
java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
at
java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
at
java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
at
java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:179)
at
java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:1024)
at
java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)
at
java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)
at
java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
at
java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
at
java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at
java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:596)
at
io.fabric8.kubernetes.internal.KubernetesDeserializer$Mapping.registerClassesFromClassLoaders(KubernetesDeserializer.java:215)
at
io.fabric8.kubernetes.internal.KubernetesDeserializer.(KubernetesDeserializer.java:90)
at
io.fabric8.kubernetes.client.utils.KubernetesSerialization.getKubernetesDeserializer(KubernetesSerialization.java:153)
at
io.fabric8.kubernetes.client.utils.KubernetesSerialization.access$000(KubernetesSerialization.java:66)
at
io.fabric8.kubernetes.client.utils.KubernetesSerialization$1.deserializerInstance(KubernetesSerialization.java:105)
at
com.fasterxml.jackson.databind.deser.DefaultDeserializationContext.deserializerInstance(DefaultDeserializationContext.java:245)
at
com.fasterxml.jackson.databind.deser.DeserializerCache.findDeserializerFromAnnotation(DeserializerCache.java:466)
at
com.fasterxml.jackson.databind.deser.DeserializerCache._createDeserializer(DeserializerCache.java:361)
at
com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCache2(DeserializerCache.java:295)
at
com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCacheValueDeserializer(DeserializerCache.java:273)
at
com.fasterxml.jackson.databind.deser.DeserializerCache.findValueDeserializer(DeserializerCache.java:173)
at
com.fasterxml.jackson.databind.DeserializationContext.findNonContextualValueDeserializer(Deser
[jira] [Commented] (CAMEL-21380) camel-salesforce: pub/sub: add ability to opt out of proxy
[ https://issues.apache.org/jira/browse/CAMEL-21380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892506#comment-17892506 ] Claus Ibsen commented on CAMEL-21380: - I have backported > camel-salesforce: pub/sub: add ability to opt out of proxy > --- > > Key: CAMEL-21380 > URL: https://issues.apache.org/jira/browse/CAMEL-21380 > Project: Camel > Issue Type: Improvement > Components: camel-salesforce >Affects Versions: 4.8.0 >Reporter: Jeremy Ross >Assignee: Jeremy Ross >Priority: Major > Fix For: 4.8.2, 4.9.0 > > > By default the underlying grpc implementation automatically uses any detected > proxy server. Need the ability to override this and not use a proxy. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (CAMEL-21381) camel k8s cannot run spring-boot on openshift
[
https://issues.apache.org/jira/browse/CAMEL-21381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler reopened CAMEL-21381:
> camel k8s cannot run spring-boot on openshift
> -
>
> Key: CAMEL-21381
> URL: https://issues.apache.org/jira/browse/CAMEL-21381
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.0
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.8.2, 4.9.0
>
>
> {code}
> Exporting application ...
> Generating fresh run data
> Exporting as Spring Boot project to: .camel-jbang-run/timer-log
> Building Kubernetes manifest ...
> Project export successful!
> Deploying to openshift ...
> Run: .camel-jbang-run/timer-log/mvnw --file .camel-jbang-run/timer-log
> package k8s:deploy
> [INFO] Scanning for projects...
> [INFO] Downloading from custom2:
> https://repository.apache.org/content/groups/snapshots/org/codehaus/mojo/maven-metadata.xml
> [INFO] Downloading from custom2:
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloaded from custom2:
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-metadata.xml
> (8.8 kB at 24 kB/s)
> [INFO] Downloading from central:
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
> [INFO] Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> (14 kB at 113 kB/s)
> [INFO] Downloaded from central:
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml (21
> kB at 164 kB/s)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.917 s
> [INFO] Finished at: 2024-10-24T07:52:12+02:00
> [INFO]
>
> [ERROR] No plugin found for prefix 'k8s' in the current project and in the
> plugin groups [org.apache.maven.plugins, org.codehaus.mojo]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21381) camel k8s cannot run spring-boot on openshift
[
https://issues.apache.org/jira/browse/CAMEL-21381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler resolved CAMEL-21381.
Resolution: Fixed
Done
> camel k8s cannot run spring-boot on openshift
> -
>
> Key: CAMEL-21381
> URL: https://issues.apache.org/jira/browse/CAMEL-21381
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.0
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.8.2, 4.9.0
>
>
> {code}
> Exporting application ...
> Generating fresh run data
> Exporting as Spring Boot project to: .camel-jbang-run/timer-log
> Building Kubernetes manifest ...
> Project export successful!
> Deploying to openshift ...
> Run: .camel-jbang-run/timer-log/mvnw --file .camel-jbang-run/timer-log
> package k8s:deploy
> [INFO] Scanning for projects...
> [INFO] Downloading from custom2:
> https://repository.apache.org/content/groups/snapshots/org/codehaus/mojo/maven-metadata.xml
> [INFO] Downloading from custom2:
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloaded from custom2:
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-metadata.xml
> (8.8 kB at 24 kB/s)
> [INFO] Downloading from central:
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
> [INFO] Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> (14 kB at 113 kB/s)
> [INFO] Downloaded from central:
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml (21
> kB at 164 kB/s)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.917 s
> [INFO] Finished at: 2024-10-24T07:52:12+02:00
> [INFO]
>
> [ERROR] No plugin found for prefix 'k8s' in the current project and in the
> plugin groups [org.apache.maven.plugins, org.codehaus.mojo]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] (CAMEL-21381) camel k8s cannot run spring-boot on openshift
[ https://issues.apache.org/jira/browse/CAMEL-21381 ]
Thomas Diesler deleted comment on CAMEL-21381:
was (Author: tdiesler):
Done
> camel k8s cannot run spring-boot on openshift
> -
>
> Key: CAMEL-21381
> URL: https://issues.apache.org/jira/browse/CAMEL-21381
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.0
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.8.2, 4.9.0
>
>
> {code}
> Exporting application ...
> Generating fresh run data
> Exporting as Spring Boot project to: .camel-jbang-run/timer-log
> Building Kubernetes manifest ...
> Project export successful!
> Deploying to openshift ...
> Run: .camel-jbang-run/timer-log/mvnw --file .camel-jbang-run/timer-log
> package k8s:deploy
> [INFO] Scanning for projects...
> [INFO] Downloading from custom2:
> https://repository.apache.org/content/groups/snapshots/org/codehaus/mojo/maven-metadata.xml
> [INFO] Downloading from custom2:
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloaded from custom2:
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-metadata.xml
> (8.8 kB at 24 kB/s)
> [INFO] Downloading from central:
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
> [INFO] Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> (14 kB at 113 kB/s)
> [INFO] Downloaded from central:
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml (21
> kB at 164 kB/s)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.917 s
> [INFO] Finished at: 2024-10-24T07:52:12+02:00
> [INFO]
>
> [ERROR] No plugin found for prefix 'k8s' in the current project and in the
> plugin groups [org.apache.maven.plugins, org.codehaus.mojo]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work started] (CAMEL-21381) camel k8s cannot run spring-boot on openshift
[
https://issues.apache.org/jira/browse/CAMEL-21381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-21381 started by Thomas Diesler.
--
> camel k8s cannot run spring-boot on openshift
> -
>
> Key: CAMEL-21381
> URL: https://issues.apache.org/jira/browse/CAMEL-21381
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.0
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.8.2, 4.9.0
>
>
> {code}
> Exporting application ...
> Generating fresh run data
> Exporting as Spring Boot project to: .camel-jbang-run/timer-log
> Building Kubernetes manifest ...
> Project export successful!
> Deploying to openshift ...
> Run: .camel-jbang-run/timer-log/mvnw --file .camel-jbang-run/timer-log
> package k8s:deploy
> [INFO] Scanning for projects...
> [INFO] Downloading from custom2:
> https://repository.apache.org/content/groups/snapshots/org/codehaus/mojo/maven-metadata.xml
> [INFO] Downloading from custom2:
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloaded from custom2:
> https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-metadata.xml
> (8.8 kB at 24 kB/s)
> [INFO] Downloading from central:
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml
> [INFO] Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> [INFO] Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> (14 kB at 113 kB/s)
> [INFO] Downloaded from central:
> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml (21
> kB at 164 kB/s)
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 0.917 s
> [INFO] Finished at: 2024-10-24T07:52:12+02:00
> [INFO]
>
> [ERROR] No plugin found for prefix 'k8s' in the current project and in the
> plugin groups [org.apache.maven.plugins, org.codehaus.mojo]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21355) LangChain4j Tools fails with direct LLM response
[ https://issues.apache.org/jira/browse/CAMEL-21355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892723#comment-17892723 ] Otavio Rodolfo Piske edited comment on CAMEL-21355 at 10/25/24 9:13 AM: I presume you are talking about, let's say, if the user pass invalid characters to the name of the function? Or is it something different? Can you please, give an example of how we could make that happen with Camel? Considering that we do not get that low level into the client API ... Additionally, it's not just a malformed response that may cause the model to decide not to invoke anything. A model is non-deterministic by design and it may decide not to call a tool even if the request is well-formed. Considering this and letting the user decide what they want to do in the absence of a tool call response is a better compromise IMHO. And, please, I am not arguing for the sake of arguing or because of stubbornness, but I do need an specific and concrete scenario. was (Author: orpiske): I presume you are talking about, let's say, if the user pass invalid characters to the name of the function? Or is it something different? Can you please, give an example of how we could make that happen with Camel? Considering that we do not get that low level into the client API ... Additionally, it's not just a malformed response that may cause the model to decide not to invoke anything. A model is non-deterministic by design and it may decide not to call a tool even if the request is well-formed. Considering this and letting the user decide what they want to do in the absence is a better compromise IMHO. And, please, I am not arguing for the sake of arguing or because of stubbornness, but I do need an specific and concrete scenario. > LangChain4j Tools fails with direct LLM response > > > Key: CAMEL-21355 > URL: https://issues.apache.org/jira/browse/CAMEL-21355 > Project: Camel > Issue Type: Bug > Components: camel-langchain4j-tools >Affects Versions: 4.8.0 >Reporter: Bruno Meseguer >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.8.2, 4.9.0 > > > The Tools component is designed to provide functions to the LLM. However the > LLM may decide not to invoke any of the given tools. > In that scenario, the LLM replies directly instead of requesting the > execution of a tool/function. The Camel Tools components seems unable to > handle such use case and throws an exception. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (CAMEL-21383) Add OIDC support for Knative Http client
[ https://issues.apache.org/jira/browse/CAMEL-21383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-21383 started by Christoph Deppisch. -- > Add OIDC support for Knative Http client > > > Key: CAMEL-21383 > URL: https://issues.apache.org/jira/browse/CAMEL-21383 > Project: Camel > Issue Type: Improvement > Components: camel-knative-http >Reporter: Christoph Deppisch >Assignee: Christoph Deppisch >Priority: Major > Fix For: 4.9.0 > > > The Knative eventing broker may use OIDC (OpenID Connect) as an authorization > protocol. Clients need to use the respective tokens to authenticate via Https > when connecting to the Knative broker in order to produce events. > > OpenID Connect (OIDC) is an identity authentication protocol that works with > OAuth 2.0 to standardize the process for authenticating and authorizing users. > Knative eventing supports OIDC access tokens that get injected as part of a > SinkBinding resource. The injection is done in the form of a volume mount on > the sink binding subject (usually the app deployment). This means the OIDC > access token is mounted as a file into the application container so Camel > client may read the token and set proper Authorization Http headers on each > request. > > The OIDC tokens may expire and get renewed by Knative eventing. The renewal > means that the volume mount is updated with the new token automatically. > In order to refresh the token the Camel Knative client must read the token > again. The Knative client options supports the token renewal on a `401 > forbidden` response from the Knative broker. Once the client has received the > forbidden answer it automatically reloads the token from the volume mount to > perform the renewal. > > As an alternative to that you may disable the token cache on the client so > the token is always read from the volume mount for each request. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21383) Add OIDC support for Knative Http client
[ https://issues.apache.org/jira/browse/CAMEL-21383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christoph Deppisch reassigned CAMEL-21383: -- Assignee: Christoph Deppisch > Add OIDC support for Knative Http client > > > Key: CAMEL-21383 > URL: https://issues.apache.org/jira/browse/CAMEL-21383 > Project: Camel > Issue Type: Improvement > Components: camel-knative-http >Reporter: Christoph Deppisch >Assignee: Christoph Deppisch >Priority: Major > Fix For: 4.9.0 > > > The Knative eventing broker may use OIDC (OpenID Connect) as an authorization > protocol. Clients need to use the respective tokens to authenticate via Https > when connecting to the Knative broker in order to produce events. > > OpenID Connect (OIDC) is an identity authentication protocol that works with > OAuth 2.0 to standardize the process for authenticating and authorizing users. > Knative eventing supports OIDC access tokens that get injected as part of a > SinkBinding resource. The injection is done in the form of a volume mount on > the sink binding subject (usually the app deployment). This means the OIDC > access token is mounted as a file into the application container so Camel > client may read the token and set proper Authorization Http headers on each > request. > > The OIDC tokens may expire and get renewed by Knative eventing. The renewal > means that the volume mount is updated with the new token automatically. > In order to refresh the token the Camel Knative client must read the token > again. The Knative client options supports the token renewal on a `401 > forbidden` response from the Knative broker. Once the client has received the > forbidden answer it automatically reloads the token from the volume mount to > perform the renewal. > > As an alternative to that you may disable the token cache on the client so > the token is always read from the volume mount for each request. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21383) Add OIDC support for Knative Http client
[ https://issues.apache.org/jira/browse/CAMEL-21383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christoph Deppisch updated CAMEL-21383: --- Description: The Knative eventing broker may use OIDC (OpenID Connect) as an authorization protocol. Clients need to use the respective tokens to authenticate via Https when connecting to the Knative broker in order to produce events. OpenID Connect (OIDC) is an identity authentication protocol that works with OAuth 2.0 to standardize the process for authenticating and authorizing users. Knative eventing supports OIDC access tokens that get injected as part of a SinkBinding resource. The injection is done in the form of a volume mount on the sink binding subject (usually the app deployment). This means the OIDC access token is mounted as a file into the application container so Camel client may read the token and set proper Authorization Http headers on each request. The OIDC tokens may expire and get renewed by Knative eventing. The renewal means that the volume mount is updated with the new token automatically. In order to refresh the token the Camel Knative client must read the token again. The Knative client options supports the token renewal on a `401 forbidden` response from the Knative broker. Once the client has received the forbidden answer it automatically reloads the token from the volume mount to perform the renewal. As an alternative to that you may disable the token cache on the client so the token is always read from the volume mount for each request. was:The Knative eventing broker may use OIDC (OpenID Connect) as an authorization protocol. Clients need to use the respective tokens to authenticate via Https when connecting to the Knative broker in order to produce events. > Add OIDC support for Knative Http client > > > Key: CAMEL-21383 > URL: https://issues.apache.org/jira/browse/CAMEL-21383 > Project: Camel > Issue Type: Improvement > Components: camel-knative-http >Reporter: Christoph Deppisch >Priority: Major > Fix For: 4.9.0 > > > The Knative eventing broker may use OIDC (OpenID Connect) as an authorization > protocol. Clients need to use the respective tokens to authenticate via Https > when connecting to the Knative broker in order to produce events. > > OpenID Connect (OIDC) is an identity authentication protocol that works with > OAuth 2.0 to standardize the process for authenticating and authorizing users. > Knative eventing supports OIDC access tokens that get injected as part of a > SinkBinding resource. The injection is done in the form of a volume mount on > the sink binding subject (usually the app deployment). This means the OIDC > access token is mounted as a file into the application container so Camel > client may read the token and set proper Authorization Http headers on each > request. > > The OIDC tokens may expire and get renewed by Knative eventing. The renewal > means that the volume mount is updated with the new token automatically. > In order to refresh the token the Camel Knative client must read the token > again. The Knative client options supports the token renewal on a `401 > forbidden` response from the Knative broker. Once the client has received the > forbidden answer it automatically reloads the token from the volume mount to > perform the renewal. > > As an alternative to that you may disable the token cache on the client so > the token is always read from the volume mount for each request. -- This message was sent by Atlassian Jira (v8.20.10#820010)
