Pasquale Congiusti

It seems the Pod cannot start, likely a registry problem. Have you followed the special instructions required for Docker Desktop? https://camel.apache.org/camel-k/2.2.x/installation/platform/docker-desktop.html

``` 2024-01-26 11:48:13 {"level":"info","ts":"2024-01-26T10:48:13Z","logger":"camel-k.controller.integration","msg":"Integration error","request-namespace":"default","request-name":"hello","api-version":"camel.apache.org/v1","kind":"Integration","ns":"default","name":"hello","reason":"Error","error-message":"Back-off pulling image \"host.docker.internal:5000/default/camel-k-kit-cmoe5nh9lrbs73afkkig@sha256:18d8f7b8ef18f8d166f51c2edac13ce116cfbfb1d23746aa4265afbd14002931\""} ``` I think the problem is with Kubernetes platform, which is not able to pull the image for some reason. Basically, Camel...

Unfortunately it's a breaking compatibility change. See: https://github.com/apache/camel-k/pull/5246#issuecomment-2009270960 - mind that what it works for you may be disruptive for another running production environment.

As mentioned in the PR, we should publish manifests accordingly to solve this issue: https://github.com/apache/camel-k/pull/5200#pullrequestreview-1906815706

Indeed. The actual way this could work is https://camel.apache.org/camel-k/2.2.x/configuration/runtime-resources.html#runtime-resource-path. However, adding the support for project volumes sounds promising. Feel free to have a look if you can contribute it.

@gansheer please, rebase against `main` as we have fixed the errored check.

@realMartinez are you actively working on this?

Okey. Removed the assignment as I may have a look at this.

I think it is the way this feature was implemented. It should not support more than one cron at the same time, as the idea is that at runtime, we...

> > Also, there is no need anymore to the [camel-k extension in camel-quarkus](https://github.com/apache/camel-quarkus/tree/main/extensions/camel-k). > > When I first saw this change, I wondered about that. > > Does this...