Luis Sergio Faria Carneiro

A scenario where this might be helpful is using multiple jsonata components in an Integration. Each one would require a template file.

@lburgazzoli I'm working around this with the following strategy: * Created the config maps for each file: ``` apiVersion: v1 data: data: file1 contents kind: ConfigMap metadata: name: cm1 ---...

According https://knative.dev/docs/serving/services/storage/, projected volumes are supported in Knative.

@lburgazzoli Now I got your point. I tested it like this: Config Maps: ``` apiVersion: v1 data: file1.txt: "{\"name\": firstName}" kind: ConfigMap metadata: name: cm1 --- apiVersion: v1 data: file2.txt:...

Editing the Cron trait and adding fallback: true solves the issues as the integration is now run with Quartz. I reported the bug because maybe if was supposed to work...

Sorry @squakez, I missed your comment in April. If we're ok with adding a field to the cron trait that will be used to create the CronJob, I can work...

I inspected the kservices and this is what I found out: - While only the jvm build is ready, the ksvc uses the jvm image and the container command is...

More information: I inspected the kubernetes events after the native image is built and found this: ``` 3m53s Normal ReasonRelatedObjectChanged integration/test Build "kit-cmj7n4tmc86c7nh4hhv0", created by Integration "test", changed phase to...

I could not reproduce the error working directly with Knative. These are the steps what I followed: - Exported the yaml files for the config maps created by camel k:...

During more experimentation, I ended up with a scenario that might have the same root cause: I created an Integration and provided less resources than it needs in the Container...