Function

Fission function

Create a language runtime environment with fission env create, set CPU/memory limits and poolsize, and attach a builder image for source builds.

Create a function with fission fn create, route HTTP traffic to it, test it, and update its code through the everyday function workflow.

Define path parameters in an HTTP trigger URL with gorilla/mux patterns and read their values inside a function via request headers.

Mount Kubernetes Secrets and ConfigMaps into a Fission function and read their values for API keys and configuration.

Pull environment images from a private registry by passing an imagePullSecret to fission environment create with –imagepullsecret.

Embed a remote URL directly in a package archive when creating functions or packages to cut creation time and improve spec portability.

Create source and deployment packages with fission package, build source archives on the cluster with a builder, and attach packages to functions.

Choose and configure a function executor (poolmgr, newdeploy, or container) with –executortype to control cold starts and per-function autoscaling.

Run an existing container image as a function with the container executor via fission function run-container, without an environment or builder.

Gradually shift HTTP traffic to a new function version with a CanaryConfig, using Prometheus health checks to auto-rollback on failure.

Install Fission with the Istio service mesh and enable automatic sidecar injection for Fission and function pods.