<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Cloud Native on Wolkwacht</title>
    <link>https://wolkwacht.nl/tags/cloud-native/</link>
    <description>Recent content in Cloud Native on Wolkwacht</description>
    <image>
      <title>Wolkwacht</title>
      <url>https://wolkwacht.nl/images/branding/feature-image.png</url>
      <link>https://wolkwacht.nl/images/branding/feature-image.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 06 Sep 2026 00:00:00 +0200</lastBuildDate>
    <atom:link href="https://wolkwacht.nl/tags/cloud-native/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>KubeBuddy: An Agentless Second Opinion for Kubernetes</title>
      <link>https://wolkwacht.nl/posts/2026-08-25_kubebuddy--an-agentless-second-opinion-for-kubernetes/</link>
      <pubDate>Sun, 06 Sep 2026 00:00:00 +0200</pubDate>
      <guid>https://wolkwacht.nl/posts/2026-08-25_kubebuddy--an-agentless-second-opinion-for-kubernetes/</guid>
      <description>&lt;p&gt;&lt;img alt=&#34;An external diagnostic drone scans a Kubernetes cluster without entering its boundary&#34; loading=&#34;lazy&#34; src=&#34;https://wolkwacht.nl/images/2026/kubebuddy-feature.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;Kubernetes is very good at reporting desired state. A Deployment can be available while its pods restart every few hours. A cluster can show green nodes while workloads have no disruption budgets, probes, resource limits, or network isolation. Dashboards show signals; they do not necessarily connect them into an operational judgment.&lt;/p&gt;
&lt;p&gt;That is the gap &lt;a href=&#34;https://kubebuddy.io/&#34;&gt;KubeBuddy&lt;/a&gt; tries to fill. The open-source KubeDeck project is a Go-based command-line scanner that connects through an existing Kubernetes context and evaluates cluster health, workloads, security, RBAC, networking, storage, and configuration. It can add provider-specific checks for AKS and GKE and emit terminal, HTML, JSON, and CSV output. There is no controller, Helm release, or long-running agent to install in the cluster.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Azure Day on Kubernetes &#43; KubeCon/CloudNativeCon Europe 2023 </title>
      <link>https://wolkwacht.nl/posts/kubeconeu/</link>
      <pubDate>Sat, 22 Apr 2023 09:56:20 +0200</pubDate>
      <guid>https://wolkwacht.nl/posts/kubeconeu/</guid>
      <description>Recap of KubeConEU 2023 and Azure Day with Kubernetes.</description>
    </item>
    <item>
      <title>AKS Edge Essentials</title>
      <link>https://wolkwacht.nl/posts/aks-edge/</link>
      <pubDate>Tue, 04 Apr 2023 09:09:51 +0200</pubDate>
      <guid>https://wolkwacht.nl/posts/aks-edge/</guid>
      <description>First look at AKS Edge essentials</description>
    </item>
    <item>
      <title>KubeCon / CloudNativeCon Europe Virtual</title>
      <link>https://wolkwacht.nl/posts/kubecon-cloudnativecon-europe-2020/</link>
      <pubDate>Mon, 17 Aug 2020 00:00:00 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/kubecon-cloudnativecon-europe-2020/</guid>
      <description>&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://wolkwacht.nl/images/2020/kubeconbanner.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;This is the first day of KubeCon + CloudNativeCon Europe Virtual. Originally this event was planned for the end of March/ beginning of April in Amsterdam. I was really looking forward to it because Amsterdam is very near where I live. Because of covid-19 is wast decided to postpone the event and finally they made it a virtual event. Despite of the fact that it is now a virtual event I’m still happy that Kubecon + CloudNativeCon is being held. I think the CNCF, sponsors, speakers and everybody that is involved with creating this event deserve kudos for organising  it. I’m ready to attend the sessions, visit the virtual booth’s and participate in this event. I will not be able to fully focus this whole week on KubeCon so I making choices in which sessions I will follow. During the conference I will share topics that interest me.&lt;/p&gt;</description>
    </item>
    <item>
      <title>KubeCon | CloudNativeCon Europe 2019 part 2</title>
      <link>https://wolkwacht.nl/posts/kubecon-cloudnativecon-europe-2019-2/</link>
      <pubDate>Tue, 11 Jun 2019 18:48:02 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/kubecon-cloudnativecon-europe-2019-2/</guid>
      <description>&lt;p&gt;As I already explained in my earlier &lt;a href=&#34;https://www.jurgenallewijn.nl/kubecon-cloudnativecon-europe-2019-1/&#34;&gt;post&lt;/a&gt;, this was my first KubeCon | CloudNativeCon that I attended. What I liked about KubeCon was the diversity in sessions and that it was often a difficult choice per time slot which session to attend. For me this congress was next to attending sessions also about networking with vendors and other attendees. There were a lot of good opportunities and I spoke to a lot of people.&lt;/p&gt;</description>
    </item>
    <item>
      <title>KubeCon / CloudNativeCon Europe 2019 part 1</title>
      <link>https://wolkwacht.nl/posts/kubecon-cloudnativecon-europe-2019-1/</link>
      <pubDate>Fri, 17 May 2019 08:38:52 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/kubecon-cloudnativecon-europe-2019-1/</guid>
      <description>&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://wolkwacht.nl/images/2019/kubeconcloudnsativecon.jpeg&#34;&gt;&lt;/p&gt;
&lt;p&gt;This year I&amp;rsquo;m going to KubeCon | CloudNativeCon which is held in Barcelona from Monday, May 20, 2019 - Thursday, May 23. This is my first KubeCon and I&amp;rsquo;m really looking forward to the sessions and the meetings I have scheduled&lt;/p&gt;
&lt;p&gt;Here is list of tips which kind of apply to every conference I have attended.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Wear comfortable shoes&lt;/li&gt;
&lt;li&gt;Take a powerbank/ adapters with you&lt;/li&gt;
&lt;li&gt;Build your agenda using the agenda builder&lt;/li&gt;
&lt;li&gt;Leave time between session. You need time to process the information you get from different sessions&lt;/li&gt;
&lt;li&gt;Take time to network with other attendees or vendors&lt;/li&gt;
&lt;li&gt;Check the sponsors on the Sponsor showcase&lt;/li&gt;
&lt;li&gt;Install the Sched app to have your schedule on your mobile&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Enjoy the event :)&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You can book your agenda via this link, &lt;a href=&#34;https://kccnceu19.sched.com/&#34;&gt;https://kccnceu19.&lt;/a&gt;&lt;a href=&#34;https://kccnceu19.sched.com/&#34;&gt;sched&lt;/a&gt;&lt;a href=&#34;https://kccnceu19.sched.com/&#34;&gt;.com/&lt;/a&gt; . Below is my schedule as it currently is within the app. I selected a session for every slot but that will not be doable as I have also meetings planned and like I said in my tips you should als to time to process the information and of course visit the booths of the sponsors. So this schedule will definitely change during the conference.&lt;/p&gt;</description>
    </item>
    <item>
      <title>k3s: Kubernetes Dashboard &#43; load balancer</title>
      <link>https://wolkwacht.nl/posts/k3s-kubernetes-dashboard-load-balancer/</link>
      <pubDate>Mon, 08 Apr 2019 19:31:14 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/k3s-kubernetes-dashboard-load-balancer/</guid>
      <description>&lt;p&gt;In &lt;a href=&#34;https://www.jurgenallewijn.nl/k3s-lightweight-kubernetes-distribution-first-experience/&#34;&gt;my post about first experience with k3s&lt;/a&gt; I blogged about setting up my k3s based cluster on Raspberry PI&amp;rsquo;s. Since that post I have added two more nodes Raspberry Pi&amp;rsquo;s and also updated to the &lt;a href=&#34;https://twitter.com/Rancher_Labs/status/1111810281443901450&#34;&gt;0.3.0&lt;/a&gt; version of k3s.&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;pi@k3s-master-1:~ $ kubectl get nodes
NAME           STATUS   ROLES    AGE     VERSION
k3s-master-1   Ready    master   4h11m   v1.13.5-k3s.1
k3s-node-1     Ready    node     129m    v1.13.5-k3s.1
k3s-node-2     Ready    node     118m    v1.13.5-k3s.1
k3s-node-3     Ready    node     119m    v1.13.5-k3s.1
pi@k3s-master-1:~ $
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Next step for me was getting the Kubernetes Dashboard up and running. I used the information from &lt;a href=&#34;https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/&#34;&gt;Web UI (Dashboard)&lt;/a&gt; First downloaded I the kubernetes-dashboard.yaml&lt;/p&gt;</description>
    </item>
    <item>
      <title>k3s: release v0.2.0 released</title>
      <link>https://wolkwacht.nl/posts/k3s-release-v0-2-0-released/</link>
      <pubDate>Sat, 09 Mar 2019 07:34:42 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/k3s-release-v0-2-0-released/</guid>
      <description>&lt;p&gt;&lt;img alt=&#34;K3S&#34; loading=&#34;lazy&#34; src=&#34;https://wolkwacht.nl/images/2019/k3s-150x137.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;Rancher has released v0.2.0.of k3s. Information of the new release is in this article. As soon as I have some time and I have added two extra nodes to the cluster, I&amp;rsquo;m going to add the cluster to my Rancher server. I have upgraded my Raspberry Pi&amp;rsquo;s to v0.2.0. The process of upgrading is really simple. Just download the new version and replace the old version of k3s with the new version and restart.&lt;/p&gt;</description>
    </item>
    <item>
      <title>k3s: Lightweight Kubernetes Distribution first experience</title>
      <link>https://wolkwacht.nl/posts/k3s-lightweight-kubernetes-distribution-first-experience/</link>
      <pubDate>Wed, 06 Mar 2019 16:25:56 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/k3s-lightweight-kubernetes-distribution-first-experience/</guid>
      <description>&lt;p&gt;&lt;img alt=&#34;K3S&#34; loading=&#34;lazy&#34; src=&#34;https://wolkwacht.nl/images/2019/k3s-150x137.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;Rancher introduced alsmost week ago k3s, a lightweight Kubernetes Distribution. In the YouTube video below you hear Shannon Williams and Darren Shepherd from Rancher talk about K3S, what it is, the usecases and demo of K3S.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://youtu.be/5-5t672vFi4&#34;&gt;https://youtu.be/5-5t672vFi4&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://github.com/rancher/k3s&#34;&gt;k3s&lt;/a&gt;is a fully compliant, production-grade Kubernetes distribution that maintains an absolutely tiny footprint. Weighing in at less than 40 MB, it only needs 512 MB of RAM to run. This means it’s perfect for all kinds of computing that requires a minimal about of memory and space.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
