riff

A function developer may want to supply code and have a platform handle the container and serving setup around it. riff provided tooling for building and running functions and applications on Kubernetes, using buildpacks, function invokers and integrations with Knative Serving. The project announced its completion in 2021. Existing workloads can carry dependencies on riff’s build and request interfaces, so moving them requires preserving those contracts rather than assuming another container-serving platform understands the same function definitions.

Current guidance

The project homepage announces completion on March 13, 2021. It describes buildpacks and function invokers alongside Knative Serving integration. This is a primary project completion notice, not an inference from a missing release or a failed URL.

For an existing installation, inventory the function invoker, build process, runtime image, routes and event sources before removing components. A function’s source code alone may not capture the HTTP or event contract implemented by its invoker. Preserve representative requests and responses, dependency versions and operational configuration so the application can be tested independently of the old platform.

Knative Serving remains a separate project to assess for container serving; it is not a promise that old riff commands, functions or deployment definitions still work. A migration may require building a normal container image, adapting the request interface and selecting eventing components separately. Compare cold-start behavior, concurrency, scale-to-zero and error handling against the original workload before changing traffic. Kubedex retains the recovered description for historical context and does not recommend a fresh installation of the completed riff platform.