Hello. You also need to use `runtimeProvider: plain-quarkus` in order to use the regular Quarkus. Also consider that sometimes quarkus folks do a bom release before Camel Quarkus to be available and they include it in future patch releases, for example 3.27.1. See this chat thread to have more info about this point [1]
Cheers, Pasquale. [1] #camel-k > ✔ Some plain-quarkus runtime versions are not available i... @ 💬 <https://camel.zulipchat.com/#narrow/channel/257299-camel-k/topic/.E2.9C.94.20Some.20plain-quarkus.20runtime.20versions.20are.20not.20available.20i.2E.2E.2E/near/543670401> On Mon, Oct 20, 2025 at 12:26 PM Ephemeris Lappis < [email protected]> wrote: > Hello. > > Trying first to change at the integration level, I've an error : > version 3.27.0 is not found ; is it really available,since I can't see > it in Central ? > > My change in my it : > > traits: > camel: > runtimeVersion: 3.27.0 > > Thanks again. > > Le lun. 20 oct. 2025 à 11:54, Pasquale Congiusti > <[email protected]> a écrit : > > > > Hello, > > you will need to update your IntegrationPlatform to extend the camel > trait > > with the given runtime provider (plain-quarkus) and version (the quarkus > > version) you want to use for all your Integrations or use an > > IntegrationProfile accordingly. Individually you can change each of your > > Integration as shown in the doc. A Camel Quarkus runtime based on 4.15.0 > is > > not yet available. I guess it will be sooner than later released, it will > > be publicly announced in a Camel blog post for sure. The latest one is > > 3.27.0 based on Camel 4.14.0 [1] > > > > Pasquale. > > > > [1] https://camel.apache.org/blog/2025/09/camel-quarkus-3.27.0/ > > > > On Mon, Oct 20, 2025 at 11:00 AM Ephemeris Lappis < > > [email protected]> wrote: > > > > > Hello. > > > > > > Thanks for your explanations. I'm looking at how it could be possible > > > to upgrade my 2.8.0 camel-k operator to use a Camel 4.15.0, but it > > > doesn't seem so easy... Do you confirm ? > > > Is the 2.9.0 available in any way ? > > > > > > Thanks again. > > > > > > Le lun. 20 oct. 2025 à 09:34, Pasquale Congiusti > > > <[email protected]> a écrit : > > > > > > > > Hello, > > > > related to your original problem, it is a bug in the Camel core [1]. > As > > > for > > > > the auto detection, it also seems to be a bug, but on Camel K side > [2]. > > > > Finally, if you want to use any more recent Camel version on Camel K, > > > > you're invited to move to `plain-quarkus` runtime provider [3] which > will > > > > begin standard in the future version of Camel K. > > > > > > > > Cheers, > > > > Pasquale. > > > > > > > > [1] https://issues.apache.org/jira/browse/CAMEL-22571 > > > > [2] https://github.com/apache/camel-k/issues/6336 > > > > [3] > > > > > > > > https://camel.apache.org/camel-k/next/running/running.html#_runtime_provider > > > > > > > > On Mon, Oct 20, 2025 at 9:24 AM Ephemeris Lappis < > > > [email protected]> > > > > wrote: > > > > > > > > > Hello. > > > > > > > > > > I don't know what JBang exactly does, but our current goal is to > > > > > evaluate the opportunity to use Camel-K and it's strong integration > > > > > with K8s, and have a convergent way of managing applications, both > our > > > > > Camel ESB exchange system and front-back applications. All our > > > > > development and devops ecosystem is based on k8s, helm and so on, > > > > > except our Camel works that are still based on a Karaf runtime > (even > > > > > if it's running as a k8s pod) and hand made tooling. > > > > > > > > > > Do you know an easy way to upgrade the Camel version (and > > > > > Camel-k/Quarkus runtime) ? > > > > > > > > > > Thanks again. > > > > > > > > > > Le sam. 18 oct. 2025 à 11:53, Claus Ibsen <[email protected]> > a > > > écrit > > > > > : > > > > > > > > > > > > Hi > > > > > > > > > > > > Ah okay so if you run via camel-k and often dependencies are not > > > > > > automatically detected, so you need to add them manually in the > file. > > > > > > Using pure camel using camel-jbang offers a better experience for > > > this > > > > > and > > > > > > is much more actively developed these days. > > > > > > > > > > > > > > > > > > On Sat, Oct 18, 2025 at 11:25 AM Ephemeris Lappis < > > > > > > [email protected]> wrote: > > > > > > > > > > > > > Hello. > > > > > > > > > > > > > > My last message was rejected yesterday. I don't know why... I > don't > > > > > > > understand why the code was not in the previous one... > Strange. I > > > put > > > > > > > the whole integration yaml in attachment. > > > > > > > > > > > > > > About the Camel version : it is pre-integrated with Camel-K > 2.8.0 > > > and > > > > > > > its Camel-K Runtime, and I'm not sure I could easily change it > for > > > a > > > > > > > more recent one... > > > > > > > > > > > > > > I hope this time you can read. > > > > > > > > > > > > > > Thanks again. > > > > > > > > > > > > > > Le ven. 17 oct. 2025 à 18:47, Claus Ibsen < > [email protected]> > > > a > > > > > écrit > > > > > > > : > > > > > > > > > > > > > > > > Hi > > > > > > > > > > > > > > > > We cannot see your code. > > > > > > > > > > > > > > > > And if you really use an old 4.8.5 camel version, then try > with > > > > > > > > newer releases like 4.14.x or 4.15.0. > > > > > > > > > > > > > > > > On Fri, Oct 17, 2025 at 6:09 PM Ephemeris Lappis < > > > > > > > [email protected]> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hello. > > > > > > > > > > > > > > > > > > I've seen that the data format for beanio is back with > Camel 4. > > > > > > > > > I'm trying to create a route in a Camel-K yaml Integration > > > file, > > > > > but > > > > > > > I've > > > > > > > > > an exception. > > > > > > > > > > > > > > > > > > It seems that the component is not able to take a string to > > > create > > > > > a > > > > > > > > > Charset object : > > > > > > > > > > > > > > > > > > org.apache.camel.RuntimeCamelException: > > > > > > > > > > org.apache.camel.NoTypeConversionAvailableException: No > type > > > > > > > converter > > > > > > > > > > available to convert from type: java.lang.String to the > > > required > > > > > > > type: > > > > > > > > > > java.nio.charset.Charset > > > > > > > > > > > > > > > > > > > > > > > > > > > The route is like : > > > > > > > > > > > > > > > > > > If I remove the encoding, all works as expected since my > system > > > > > > > charset is > > > > > > > > > UTF-8. > > > > > > > > > > > > > > > > > > What's wrong with my yaml ? > > > > > > > > > > > > > > > > > > I've also noticed that the beanio data format is not > > > automatically > > > > > > > added as > > > > > > > > > a dependency just like the json that I also use in the same > > > > > > > Integration. > > > > > > > > > Why ? > > > > > > > > > > > > > > > > > > Thanks. > > > > > > > > > > > > > > > > > > Regards. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > Claus Ibsen > > > > > > > > > > > > > > < > > > > > > > > > > > > > > > > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail > > > > > > > > > > > > > > > Sans virus.www.avast.com > > > > > > > < > > > > > > > > > > > > > > > > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail > > > > > > > > > > > > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Claus Ibsen > > > > > > > > >
