<?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>Devops on Wolkwacht</title>
    <link>https://wolkwacht.nl/tags/devops/</link>
    <description>Recent content in Devops 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/devops/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>Is Azure Container Apps Eating AKS&#39;s Lunch for Smaller Workloads?</title>
      <link>https://wolkwacht.nl/posts/2026-09-04_is-azure-container-apps-eating-akss-lunch-for-smaller-workloads/</link>
      <pubDate>Fri, 04 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/2026-09-04_is-azure-container-apps-eating-akss-lunch-for-smaller-workloads/</guid>
      <description>&lt;p&gt;&lt;img alt=&#34;A small set of containerized services chooses between a lightweight managed platform and a more sophisticated Kubernetes platform&#34; loading=&#34;lazy&#34; src=&#34;https://wolkwacht.nl/images/2026/aca-vs-aks-feature.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;Kubernetes has become so familiar that many teams don&amp;rsquo;t choose to adopt it anymore; they just start using it. When a new internal API appears, someone sets up an AKS cluster, and within weeks, the team manages node pools, upgrade channels, ingress, identity, policies, observability, and a backlog of Helm charts. None of these decisions are incorrect, but the issue is that the workload might never have required a Kubernetes platform in the first place.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Devopsdays Amsterdam 2023</title>
      <link>https://wolkwacht.nl/posts/devopsdays2023/</link>
      <pubDate>Tue, 27 Jun 2023 13:59:17 +0200</pubDate>
      <guid>https://wolkwacht.nl/posts/devopsdays2023/</guid>
      <description>Recap of Devopsdays Amsterdam 2023</description>
    </item>
  </channel>
</rss>
