Deployment models of nuclio #2937
Replies: 2 comments 1 reply
-
@dberardo-com sorry for the delayed response.
Nuclio supports 2 cron job modes:
The mode can be changed in the values.yaml file, on the platform configuration (see https://github.com/nuclio/nuclio/blob/development/hack/k8s/helm/nuclio/values.yaml#L478).
The While we don't have extensive documentation on this, you can check the docs in https://github.com/v3io/scaler for further information. |
Beta Was this translation helpful? Give feedback.
-
also a related question: is it possible to start the build function jobs (e.g. kaniko) in the namespace of the function itself? at the moment the build job is created in the dashboard's namespace and that might be problematic under a security and resourcestandpoint. the kaniko build job is indeed quite resource expensive ... is there any slimmer image / solution to build the image ? |
Beta Was this translation helpful? Give feedback.
-
The project README states:
Once deployed, you can terminate the Nuclio Dashboard and Controller services and Nuclio functions will still run and scale perfectly.
How about cron triggers? how are such events handled by Nuclio? who is the source of such events? i dont see any k8s CronJob being deployed, thats why i ask
Also in the same section:
For this purpose, Nuclio has a "Scaler" service. This handles all matters of scaling to zero and, more importantly, from zero.
Is there any doc about the scaler service at the moment? i believe that this service is currently embedded within the dashboard service ? (since i see only 2 pods being deployed in k8s (dashboard + controller)
``
Beta Was this translation helpful? Give feedback.
All reactions