AutoScaling - Quarkus, KNative #1002
-
|
Using Karavan, Openshift, Camel Jang with below properties and trying to get to the default behaviour which is if the requests are idle, the Openshift would scale down the container to Zero. But as such it is not happenning. I tried explicitly setting the value quarkus.knative.scale-to-zero-enabled=true but still no luck? Any guidance would be helpful. camel.health.enabled=true image build propertiesquarkus.container-image.build=true deployment propertiesquarkus.kubernetes.deploy=true ############## |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 9 replies
-
|
I am not an expert on Knative but I believe that it should be Openshift Serverless installed on OpenShift for that |
Beta Was this translation helpful? Give feedback.
-
|
In my case the Red Hat OpenShift Serverless is already installed. One more thing to worth mention, with the above set of properties, I see a configMap that is getting created with empty keys/values. not sure if all the quarkus.knative.* properties can be leveraged as part of the Karavan's project config? I was assuming that should be the case. But just wanted to mention atleast in my scenario, the below configs doesn't really seem to matter. Do I've to include any thing else in the camel.jbang.dependencies property? quarkus.knative.min-scale=0 |
Beta Was this translation helpful? Give feedback.
-
|
You need to export as a quarkus based project, karavan exports as camel-main only. And you need to adjust the build script that does the camel-jbang export |
Beta Was this translation helpful? Give feedback.
-
|
The doc for exporting to quarkus is here |
Beta Was this translation helpful? Give feedback.
-
|
Also see the quarkus docs for knative |
Beta Was this translation helpful? Give feedback.
-
|
As part of the application.properties in Karavan project, there is this below properties that I've already used. I don't think we have to explicitly specify the runtime version again. However with the below configs in place, the Knative stuff is not working as expected. camel.jbang.quarkusVersion=3.5.2 |
Beta Was this translation helpful? Give feedback.
-
|
Well karavan does not support knative directly OOTB - You can export the project to quarkus, and try locally to see what it takes to make that work with your knative platform. |
Beta Was this translation helpful? Give feedback.
-
|
Hmm...one thing I want to highlight. In the above configurations there is one property quarkus.kubernetes.deployment-target=knative. When I build the application (which comprises of just one camel rest component and logs it out ) and export it to Openshift, it is indeed deployed as serverless meaning I can see it. You can refer the screen shot below. This tells me that the packaging has been deployed as serverless for sure. However, I was trying to test if it is truly serverless by checking the default behavior where in, if the traffic is not active for more than 30 secs, the pod should scale down to zero which was not happening. 
On a separate stream, I've build KNative apps using Quarkus and deployed them successfully which were scaling down to zero. I want to check if Karavan packaging can also get me to the same behaviour and if so it would be a great feature. |
Beta Was this translation helpful? Give feedback.
-
|
Scale to zero depends on what camel components you use as the source(s). |
Beta Was this translation helpful? Give feedback.
-
|
I'm using camel rest. I assume it can be scaled down to zero? |
Beta Was this translation helpful? Give feedback.
Well karavan does not support knative directly OOTB - You can export the project to quarkus, and try locally to see what it takes to make that work with your knative platform.