<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gaurav Gahlot on Fission</title><link>https://deploy-preview-295--fission-website.netlify.app/author/gaurav-gahlot/</link><description>Recent content in Gaurav Gahlot on Fission</description><generator>Hugo</generator><language>en</language><atom:link href="https://deploy-preview-295--fission-website.netlify.app/author/gaurav-gahlot/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes Response Engine: Falcosidekick + Fission</title><link>https://deploy-preview-295--fission-website.netlify.app/blog/falcosidekick-response-engine-fission/</link><pubDate>Wed, 01 Sep 2021 00:00:00 +0000</pubDate><guid>https://deploy-preview-295--fission-website.netlify.app/blog/falcosidekick-response-engine-fission/</guid><description>&lt;blockquote&gt;
&lt;p&gt;This blog was originally published on &lt;a href="https://falco.org/blog/falcosidekick-response-engine-part-9-fission/"&gt;Falco website&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;This blog post is part of a series of articles about how to create a &lt;code&gt;Kubernetes&lt;/code&gt; response engine with &lt;code&gt;Falco&lt;/code&gt;, &lt;code&gt;Falcosidekick&lt;/code&gt; and a &lt;code&gt;FaaS&lt;/code&gt;.&lt;/em&gt;
The earlier posts in this series, show how to use Kubeless, Argo, Knative, and others to trigger a resource after getting input from Falcosidekick.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;p&gt;Recently, Falcosidekick received a new output type support for &lt;a href="https://github.com/falcosecurity/falcosidekick/pull/255"&gt;Fission&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;In this blog post, we will cover using &lt;code&gt;Falcosidekick&lt;/code&gt; and &lt;code&gt;Fission&lt;/code&gt; 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 &lt;a href="https://deploy-preview-295--fission-website.netlify.app/docs/"&gt;here&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Fission WebSocket Sample</title><link>https://deploy-preview-295--fission-website.netlify.app/blog/fission-websocket-sample/</link><pubDate>Fri, 11 Jun 2021 10:50:51 +0530</pubDate><guid>https://deploy-preview-295--fission-website.netlify.app/blog/fission-websocket-sample/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;In this post we will look into how we can develop a simple a web socket based chat application using Fission functions.
Fission&amp;rsquo;s &lt;a href="https://github.com/fission/environments/tree/master/nodejs"&gt;NodeJS environment&lt;/a&gt; now has built in support for &lt;a href="https://datatracker.ietf.org/doc/html/rfc6455"&gt;WebSocket&lt;/a&gt;.
So, we are going to use this environment to power our simple web based chat application.&lt;/p&gt;
&lt;p&gt;Let&amp;rsquo;s first understand how this is going to work.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://deploy-preview-295--fission-website.netlify.app/images/fission-websocket-sample.png" alt="architecture"&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;We start by creating a NodeJS environment using the &lt;a href="https://github.com/fission/environments/pkgs/container/node-env"&gt;fission/nodejs-env&lt;/a&gt; Docker image.&lt;/li&gt;
&lt;li&gt;Then we create a fission function for with &lt;a href="https://github.com/fission/examples/blob/main/miscellaneous/websocket/broadcast.js"&gt;broadcast.js&lt;/a&gt;.
It is this piece of code that will broadcast a message to all connected clients.&lt;/li&gt;
&lt;li&gt;Next, we will create an &lt;a href="https://fission.io/docs/usage/triggers/http-trigger/"&gt;HTTP trigger&lt;/a&gt; for the above created function.&lt;/li&gt;
&lt;li&gt;We then update our chat application to connect over the route, we just created.&lt;/li&gt;
&lt;li&gt;We will also create a function to host the this chat application.&lt;/li&gt;
&lt;li&gt;As you send a message from one chat window, the function will be triggered and the message will be broadcasted to all connected clients.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We will cover two approaches using which you can test this setup.&lt;/p&gt;</description></item></channel></rss>