Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

STACKIT Functions Concepts

With STACKIT Functions, you can package and deploy your code as containers, which are automatically scaled in response to incomming HTTP requests.

STACKIT Functions requires a container registry to store container images in. You can bring your own container registry, or, if you don’t have one yet, you can use the STACKIT Container Registry.

STACKIT Functions resources

Within STACKIT Functions, there are three main “resources” you can interact with:

  • A “Function” is the interface for your code. It mainly consists of an unique URL to which it’s deployed, and serves as the “identity” of your code, when communicating with external services.

  • A “Revision” is the implementation of your code. It holds all the configuration related to executing your code, such as what OCI image and environment variables to use. A Function has only one current revision deployed, while the rest of the revisions serve as version history of your application.

  • A “Registry” holds the credentials used for pulling container images. You can share a registry configuration between multiple revisions.

STACKIT Functions CLI

The STACKIT Functions CLI (sfn) is the main way in which you interact with STACKIT Functions.

The CLI works with a “manifest” file, called stackit-functions.yaml, which holds all the information needed to build a new function image and deploy it as a new revision.

You can bootstrap new functions using the official STACKIT Functions templates. This is done using the sfn function create command.

You can build runnable container images from those templates, using the STACKIT Functions builder. This is done using the sfn function build command or the --build flag.

You can then push the image to your container registry and deploy the function to the STACKIT Functions runtime, using the STACKIT Functions CLI. This is done using the sfn function deploy command.

STACKIT Functions runtime

The STACKIT Functions runtime is built on top of Knative, a CNCF project for running serverless functions on top of Kubernetes.

When you deploy a function to STACKIT Functions, our runtime takes care of creating the relevant Knative configurations and making your function accessible at a public URL.