Kubernetes Response Engine: Falcosidekick + Fission

Wed, 01 Sep 2021 00:00:00 +0000

This blog was originally published on Falco website.

This blog post is part of a series of articles about how to create a Kubernetes response engine with Falco, Falcosidekick and a FaaS. The earlier posts in this series, show how to use Kubeless, Argo, Knative, and others to trigger a resource after getting input from Falcosidekick.

Recently, Falcosidekick received a new output type support for Fission.

In this blog post, we will cover using Falcosidekick and Fission to detect and delete a compromised pod in a Kubernetes cluster. We will briefly talk about Fission in this blog, however, you can check the complete documentation here.

Fission WebSocket Sample

Fri, 11 Jun 2021 10:50:51 +0530

Introduction

Recommended: the streaming WebSocket path. Since Fission v1.26.0, WebSocket is first-class for every environment through the streaming invocation path (fission fn create ... --streaming --streamingprotocol websocket) — not just the NodeJS/Python built-in support this post describes. The router upgrades the connection and holds the function pod for the socket’s lifetime, so you no longer need the event-based keepalive mechanism (the Python socket_tracker.py / fetcher /wsevent endpoints), which is now deprecated. The main(ws, clients) model below is unchanged. See Streaming responses for the current approach.

Gaurav Gahlot on Fission

Kubernetes Response Engine: Falcosidekick + Fission

Fission WebSocket Sample

Introduction