<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kubernetes on Erwin Staal</title>
    <link>https://staal-it.nl/tags/kubernetes/</link>
    <description>Recent content in Kubernetes on Erwin Staal</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>KVK: Staal IT, 56920202 - Copyright © 2025</copyright>
    <lastBuildDate>Tue, 16 Jun 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://staal-it.nl/tags/kubernetes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Autoscaling .NET Core Azure Functions on Kubernetes</title>
      <link>https://staal-it.nl/posts/autoscaling-your-azure-function-on-kubernetes/</link>
      <pubDate>Tue, 16 Jun 2020 00:00:00 +0000</pubDate>
      
      <guid>https://staal-it.nl/posts/autoscaling-your-azure-function-on-kubernetes/</guid>
      <description>Everyone who worked with containers on Kubernetes probably agrees that there is a pretty steep learning curve in the beginning. Once you overcome that, you&amp;rsquo;ll find that it&amp;rsquo;s an awesome and very capable product and that it will make your life better (when used in the right context of-course). One area where Kubernetes is not so great is event-based autoscaling. That&amp;rsquo;s where KEDA comes in. KEDA stands for Kubernetes-based Event-driven Autoscaler.</description>
    </item>
    
    <item>
      <title>My k3s OpenFaaS Raspberry Pi cluster</title>
      <link>https://staal-it.nl/posts/my-k3s-openfaas-raspberry-pi-cluster/</link>
      <pubDate>Tue, 10 Sep 2019 00:00:00 +0000</pubDate>
      
      <guid>https://staal-it.nl/posts/my-k3s-openfaas-raspberry-pi-cluster/</guid>
      <description>A few months ago I build a Raspberry Pi cluster running K3S. I build it because I wanted to have a nice environment the learn more about Kubernetes and OpenFaas. It always feels nice to have something you can actually touch in this all software world I normally live in. After tweeting and giving a session about my OpenFaas Raspberry Pi cluster people started asking what parts the cluster consists of and what software I use to run it.</description>
    </item>
    
    <item>
      <title>Creating a simple OpenFaas template</title>
      <link>https://staal-it.nl/posts/creating-a-simple-openfaas-template/</link>
      <pubDate>Sat, 11 May 2019 00:00:00 +0000</pubDate>
      
      <guid>https://staal-it.nl/posts/creating-a-simple-openfaas-template/</guid>
      <description>Whenever you want to create a new function to run on OpenFaas your starting point would be an OpenFaas template. OpenFaas has a template engine build-in which can create new functions in a given programming language. There are the official/default templates and there are templates in the store provided by the community. If a language you would like to use isn’t available or it doesn’t suite your needs, you can always write your own!</description>
    </item>
    
    <item>
      <title>Your first .NET Core Serverless function on OpenFaas</title>
      <link>https://staal-it.nl/posts/your-first-net-core-serverless-function-on-openfaas/</link>
      <pubDate>Wed, 08 May 2019 00:00:00 +0000</pubDate>
      
      <guid>https://staal-it.nl/posts/your-first-net-core-serverless-function-on-openfaas/</guid>
      <description>In my previous blog I described how to set-up OpenFaas on a Kubernetes cluster with a little help from Rancher. Now it’s time to deploy our first serverless function. In this blog we’ll create and deploy a .NET Core function that reads a bit of config using both an environment variable and Kubernetes secrets.
Creating your first function In the previous blog we installed the OpenFaas cli. If you didn’t already, here are the instructions.</description>
    </item>
    
  </channel>
</rss>
