Serverless naming camelcase10/28/2022 You can use nodejs12, nodejs14, python38, or python39. Time, in seconds, after which the system cancels the request to invoke the FunctionĮnvironment used to run the Function. See the detailed descriptions of these fields: Field When the image creation finishes successfully, FC creates a Deployment that uses the newly built image.įC creates a Service that points to the Deployment.įC creates a HorizontalPodAutoscaler that automatically scales the number of Pods in the Deployment based on the observed CPU utilization.įC waits for the Deployment to become ready. The Job then pushes this image to a Docker registry.įC monitors the Job status. The Job creates a Pod which builds the production Docker image based on the Function's definition. This CR contains the Function definition (business logic that you want to execute) and information on the environment on which it should run.īefore the Function can be saved or modified, it is first updated and then verified by the defaulting and validation webhooks respectively.įunction Controller (FC) detects the new, validated Function CR.įC creates a ConfigMap with the Function definition.īased on the ConfigMap, FC creates a Kubernetes Job that triggers the creation of a Function image. Ĭreate a Function either through the UI or by applying a Function custom resource (CR). Also, if you apply custom LimitRanges for a new Namespace, they must be higher than or equal to the limits for building Jobs' resources. If you create a new Namespace, do not disable sidecar injection in it as Serverless requires Istio for other resources to communicate with Functions correctly.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |