Mert Öztürk
Mert Öztürk
> this one looks suspiciously time consuming... My exact reaction. 🥲 I am 100% there is something wrong here. This simple process cannot take that long if everything is configured...
Do/would you guys have rather similar slow start-up times if you tried out exactly what I did? Is there anything you are suspicious of? This simply can't be the norm....
I was able to test some simple Camel-K examples or even some pure Camel Quarkus examples as @squakez suggested [here](https://github.com/apache/camel-k/issues/4192#issuecomment-1489828392). But my startup times are still nowhere near the sub...
What was the runtime base image we were using before eclipse:temurin? Maybe I can try deploying the same integrations with that base image to see whether it is actually due...
Apart from the default base image eclipse:temurin that comes with version 1.12.0, I also tried the same flow with openjdk:slim but the startup times don't seem to show any improvements......
Thanks for the replies! Yes, @essobedo, you are right. I have been using the JVM mode all along. @squakez This is super strange... What might be causing me to have...
Thanks for the reply! I tested this same flow with the same integration specs in two different brand-new clusters; one on GKE, and the other on Azure. Both clusters have...
Do you happen to have any updates about this issue? @squakez I tried resetting all kits and starting from scratch. Multiple times actually, in different clusters and environments. I can't...
Can we have the same feature in the `prometheus` trait as well please? 🙏🏻