lburgazzoli edited a comment on issue #223: Fix #222: initial implementation of native cron support URL: https://github.com/apache/camel-k-runtime/pull/223#issuecomment-572511391 > Good point, but would you remove all quartz libraries on the operator side? > Yes, I think in case we want to leverage k8s scheduler we can replace the discovered dependencies with what make more sense for us so in this case quartz --> timer. BTW, we should also try to determine if you have a single route and in such case we can apply the magic, otherwise we should just go for standard deployment. > I did minimal variations to make sure an user can switch from kube-scheduled mode to standard mode easily (potentially even without changes in the library path). > Guess this can be controlled by a trait so the `auto` mode would do the magic but if you need fine grained control, then you can use the trait to influence the level of the magic > I've overridden the required fields, keeping other user settings on the endpoints.. even if I can't find something relevant that an user may customize on quartz. There are some headers added on the exchanges, that can be faked in case. I think that if you want k8s scheduler, then you do not care about headers generated by the camel components, if you want them, probably you need to keep your pod running as the headers won't be what you expect (i.e. the number of fired event will allays be just 1)
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
