<?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>Kubernetes on Wolkwacht</title>
    <link>https://wolkwacht.nl/tags/kubernetes/</link>
    <description>Recent content in Kubernetes 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>Sat, 26 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://wolkwacht.nl/tags/kubernetes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>From OrbStack to AKS: Installing Dapr on a Managed Cluster</title>
      <link>https://wolkwacht.nl/posts/from-orbstack-to-aks-installing-dapr-on-a-managed-cluster/</link>
      <pubDate>Sat, 26 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/from-orbstack-to-aks-installing-dapr-on-a-managed-cluster/</guid>
      <description>&lt;p&gt;&lt;img alt=&#34;A Dapr-enabled application moving from a local Kubernetes workstation to a managed AKS cluster&#34; loading=&#34;lazy&#34; src=&#34;https://wolkwacht.nl/images/2026/dapr-orbstack-to-aks-feature.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;Transferring a Dapr-enabled application from local Kubernetes to AKS should be straightforward. The annotations, app ID, application port, sidecar API, and workload manifest stay familiar. The key difference is ownership: a temporary local setup transforms into a shared runtime that requires a version policy, availability plan, network access, identity strategy, and support structure.&lt;/p&gt;
&lt;p&gt;This post moves the sample from &lt;a href=&#34;https://wolkwacht.nl/posts/installing-dapr-on-kubernetes-locally-with-orbstack/&#34;&gt;Installing Dapr on Kubernetes Locally with OrbStack&lt;/a&gt; to an existing AKS cluster. We will compare the open-source installation path with the AKS Dapr extension, install the extension, verify the control plane, and deploy the same NGINX workload.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Installing Dapr on Kubernetes Locally with OrbStack</title>
      <link>https://wolkwacht.nl/posts/installing-dapr-on-kubernetes-locally-with-orbstack/</link>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/installing-dapr-on-kubernetes-locally-with-orbstack/</guid>
      <description>&lt;p&gt;&lt;img alt=&#34;A developer workstation running a local Kubernetes cluster with an application and Dapr sidecar&#34; loading=&#34;lazy&#34; src=&#34;https://wolkwacht.nl/images/2026/dapr-orbstack-feature.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;To quickly grasp Dapr on Kubernetes, it’s best to start locally rather than with an AKS cluster. Local setup allows for rapid pod creation in seconds, minimizes the consequences of mistakes, and keeps all control-plane components easily accessible for inspection.&lt;/p&gt;
&lt;p&gt;In this post, we&amp;rsquo;ll demonstrate setting up OrbStack&amp;rsquo;s single-node Kubernetes cluster on macOS, installing Dapr in development mode, examining the creation process, deploying a simple web app with a sidecar, and accessing it via Dapr&amp;rsquo;s HTTP API. The same annotations and runtime model apply to AKS later, with only differences in the platform and installation approach.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Dapr on Kubernetes and AKS Series</title>
      <link>https://wolkwacht.nl/dapr-on-aks-series/</link>
      <pubDate>Sun, 13 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://wolkwacht.nl/dapr-on-aks-series/</guid>
      <description>&lt;h1 id=&#34;dapr-on-kubernetes-and-aks&#34;&gt;Dapr on Kubernetes and AKS&lt;/h1&gt;
&lt;p&gt;Dapr gives applications a consistent set of APIs for common distributed-systems concerns while leaving the backing infrastructure replaceable. This series starts with the mental model, builds a fast local development loop, moves the same workload to Azure Kubernetes Service, and then works through the building blocks and production concerns.&lt;/p&gt;
&lt;p&gt;The series is written for developers and platform engineers who already know the basics of Kubernetes but are new to Dapr. Each post stands on its own; reading in order gives you the smoothest path from first principles to production.&lt;/p&gt;</description>
    </item>
    <item>
      <title>What Is Dapr, and Why Run It on Kubernetes?</title>
      <link>https://wolkwacht.nl/posts/what-is-dapr-and-why-run-it-on-kubernetes/</link>
      <pubDate>Sun, 13 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/what-is-dapr-and-why-run-it-on-kubernetes/</guid>
      <description>&lt;p&gt;&lt;img alt=&#34;A cloud-native application and its Dapr sidecar connect to state, messaging, secrets, and services&#34; loading=&#34;lazy&#34; src=&#34;https://wolkwacht.nl/images/2026/dapr-on-aks-part-1-feature.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;Every distributed application gathers various plumbing components. One service requires retries and timeouts, another needs a message broker client, and a third must store some state, retrieve secrets, or discover other services. Over time, each team ends up with a unique set of client libraries, connection handling methods, telemetry, and failure behaviors.&lt;/p&gt;
&lt;p&gt;Dapr, the Distributed Application Runtime, provides a uniform API for the underlying infrastructure. Your application communicates with a local Dapr process via HTTP or gRPC. Dapr then interacts with services, the state store, the broker, the secret store, or other components on your application&amp;rsquo;s behalf. While the application retains control of its business logic, Dapr offers reusable capabilities for building distributed applications.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Secrets Management Showdown: Azure Key Vault CSI Driver vs. External Secrets Operator</title>
      <link>https://wolkwacht.nl/posts/2026-09-05_secrets-management-showdown--azure-key-vault-csi-driver-vs-external-secrets-operator/</link>
      <pubDate>Wed, 09 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/2026-09-05_secrets-management-showdown--azure-key-vault-csi-driver-vs-external-secrets-operator/</guid>
      <description>&lt;p&gt;&lt;img alt=&#34;Two secrets-management paths lead from a secure vault into Kubernetes workloads&#34; loading=&#34;lazy&#34; src=&#34;https://wolkwacht.nl/images/2026/feature.svg&#34;&gt;&lt;/p&gt;
&lt;p&gt;The real question is not whether to use the Azure Key Vault provider for the Secrets Store CSI Driver or the External Secrets Operator (ESO). Instead, it&amp;rsquo;s whether your workload should access secret data as &lt;strong&gt;mounted files&lt;/strong&gt; or via &lt;strong&gt;native Kubernetes Secret objects&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;That choice influences application design, rotation, incident handling, RBAC, observability, Helm compatibility, and GitOps. In short: &lt;strong&gt;CSI offers a more secure default for applications that consume files; ESO provides a more practical platform default when Kubernetes-native compatibility is a priority.&lt;/strong&gt; This decision involves both GitOps and security considerations.&lt;/p&gt;</description>
    </item>
    <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>Secure Azure Kubernetes Service (AKS)</title>
      <link>https://wolkwacht.nl/posts/secure-azure-kubernetes-service-aks/</link>
      <pubDate>Thu, 13 Aug 2026 11:01:01 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/secure-azure-kubernetes-service-aks/</guid>
      <description>Azure Kubernetes Service (AKS) removes most of the undifferentiated heavy lifting of running Kubernetes, but it does not remove your responsibility for securing what runs on top of it.</description>
    </item>
    <item>
      <title>Reducing AKS Costs: Autoscaling, Spot Nodes, Rightsizing, and FinOps Practices</title>
      <link>https://wolkwacht.nl/posts/reducing-aks-costs-autoscaling-spot-nodes-rightsizing-and-finops-practices/</link>
      <pubDate>Thu, 23 Jul 2026 11:01:01 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/reducing-aks-costs-autoscaling-spot-nodes-rightsizing-and-finops-practices/</guid>
      <description>Introduction: Cost Is an Outcome of Scheduling Decisions</description>
    </item>
    <item>
      <title>Running AI Workloads on Azure Kubernetes Service: From Platform Control to Model Serving</title>
      <link>https://wolkwacht.nl/posts/running-ai-workloads-on-azure-kubernetes-service-from-platform-control-to-model-serving/</link>
      <pubDate>Fri, 26 Jun 2026 07:31:53 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/running-ai-workloads-on-azure-kubernetes-service-from-platform-control-to-model-serving/</guid>
      <description>Most teams begin their AI journey by using a managed model API. This approach works initially but can become problematic when costs become…</description>
    </item>
    <item>
      <title>Azure Kubernetes Application Network, Part 3: AI Gateway, Observability and Production Fit</title>
      <link>https://wolkwacht.nl/posts/azure-kubernetes-application-network-part-3-ai-gateway-observability-and-production-fit/</link>
      <pubDate>Wed, 10 Jun 2026 06:14:44 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/azure-kubernetes-application-network-part-3-ai-gateway-observability-and-production-fit/</guid>
      <description>Part 1 introduced AppNet, while Part 2 demonstrated its use in zero-trust and multi-cluster patterns. This concluding section explores a…</description>
    </item>
    <item>
      <title>Azure Kubernetes Application Network, Part 2: Zero-Trust and Multi-Cluster Patterns</title>
      <link>https://wolkwacht.nl/posts/azure-kubernetes-application-network-part-2-zero-trust-and-multi-cluster-patterns/</link>
      <pubDate>Sun, 07 Jun 2026 15:18:29 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/azure-kubernetes-application-network-part-2-zero-trust-and-multi-cluster-patterns/</guid>
      <description>In Part 1, we discussed the AppNet architecture, setup process, and waypoint model. This second part shifts focus from mechanics to…</description>
    </item>
    <item>
      <title>Azure Kubernetes Application Network, Part 1: What AppNet Is and How to Get Started</title>
      <link>https://wolkwacht.nl/posts/azure-kubernetes-application-network-part-1-what-appnet-is-and-how-to-get-started/</link>
      <pubDate>Thu, 04 Jun 2026 11:00:05 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/azure-kubernetes-application-network-part-1-what-appnet-is-and-how-to-get-started/</guid>
      <description>The space between &amp;#39;we have ingress&amp;#39; and &amp;#39;we run a full service mesh with sidecars on every pod&amp;#39; has always been a challenging middle…</description>
    </item>
    <item>
      <title>When Your Cluster Isn’t Sufficient: Introducing Virtual Pools in AKS</title>
      <link>https://wolkwacht.nl/posts/when-your-cluster-isnt-sufficient-introducing-virtual-pools-in-aks/</link>
      <pubDate>Sun, 22 Mar 2026 08:32:23 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/when-your-cluster-isnt-sufficient-introducing-virtual-pools-in-aks/</guid>
      <description>There’s a moment in every Kubernetes journey when the cluster begins to feel… heavy. Not broken, not misconfigured, but stretched in ways…</description>
    </item>
    <item>
      <title>GitOps on Azure Kubernetes Service: Building a Production-Ready Platform with Flux</title>
      <link>https://wolkwacht.nl/posts/gitops-on-azure-kubernetes-service-building-a-production-ready-platform-with-flux/</link>
      <pubDate>Wed, 18 Mar 2026 07:42:06 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/gitops-on-azure-kubernetes-service-building-a-production-ready-platform-with-flux/</guid>
      <description>Kubernetes platforms seldom fail due to the technology itself; instead, failures are usually caused by operational issues.</description>
    </item>
    <item>
      <title>When Kubernetes Lies:</title>
      <link>https://wolkwacht.nl/posts/when-kubernetes-lies/</link>
      <pubDate>Thu, 19 Feb 2026 07:29:00 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/when-kubernetes-lies/</guid>
      <description>Truth inside AKS with Inspektor Gadget</description>
    </item>
    <item>
      <title>Operating AKS from your workstation</title>
      <link>https://wolkwacht.nl/posts/operating-aks-from-your-workstation/</link>
      <pubDate>Sun, 30 Nov 2025 13:04:13 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/operating-aks-from-your-workstation/</guid>
      <description>Inside Microsoft’s New AKS Desktop</description>
    </item>
    <item>
      <title>Beyond the Cloud: Running Kubernetes with Talos: Comparing Talos, k3s, AKS, and EKS</title>
      <link>https://wolkwacht.nl/posts/beyond-the-cloud-running-kubernetes-with-talos-comparing-talos-k3s-aks-and-eks/</link>
      <pubDate>Tue, 25 Nov 2025 07:53:31 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/beyond-the-cloud-running-kubernetes-with-talos-comparing-talos-k3s-aks-and-eks/</guid>
      <description>“If Kubernetes is the engine, Talos is the chassis built specifically for it.”</description>
    </item>
    <item>
      <title>Azure Kubernetes Chronicles 12: The Future of Multi-Cluster</title>
      <link>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-12-the-future-of-multi-cluster/</link>
      <pubDate>Tue, 28 Oct 2025 13:06:57 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-12-the-future-of-multi-cluster/</guid>
      <description>Fleet, Arc, sovereign clouds, and the edge-first world of 2030</description>
    </item>
    <item>
      <title>Using the AKS-MCP Server in Day-to-Day Operations</title>
      <link>https://wolkwacht.nl/posts/using-the-aks-mcp-server-in-day-to-day-operations/</link>
      <pubDate>Thu, 23 Oct 2025 06:26:36 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/using-the-aks-mcp-server-in-day-to-day-operations/</guid>
      <description>Azure Kubernetes Service (AKS) has long been the leading platform for containerized workloads on Microsoft Azure. While AKS offers…</description>
    </item>
    <item>
      <title>Azure Kubernetes Chronicles 11: Governing the Chaos</title>
      <link>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-11-governing-the-chaos/</link>
      <pubDate>Tue, 21 Oct 2025 07:57:15 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-11-governing-the-chaos/</guid>
      <description>Unifying identity, policy, networking, and observability across clouds and edge</description>
    </item>
    <item>
      <title>Azure Kubernetes Chronicles 10: Kubernetes at the Edge with k3s</title>
      <link>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-10-kubernetes-at-the-edge-with-k3s/</link>
      <pubDate>Mon, 13 Oct 2025 09:28:48 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-10-kubernetes-at-the-edge-with-k3s/</guid>
      <description>From Raspberry Pi retail stores to 5G towers — the hidden force reshaping enterprise IT</description>
    </item>
    <item>
      <title>Azure Kubernetes Security Demystified: From Nodes to Pods</title>
      <link>https://wolkwacht.nl/posts/azure-kubernetes-security-demystified-from-nodes-to-pods/</link>
      <pubDate>Mon, 06 Oct 2025 09:21:22 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/azure-kubernetes-security-demystified-from-nodes-to-pods/</guid>
      <description>&lt;h2 id=&#34;azure-kubernetes-security-demystified-from-nodes-topods&#34;&gt;Azure Kubernetes Security Demystified: From Nodes to Pods&lt;/h2&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://cdn-images-1.medium.com/max/800/1*TaWt7QA5dk2vpOJm78Oi9w.png&#34;&gt;&lt;/p&gt;
&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Kubernetes has become the standard for hosting containerized applications, with Azure Kubernetes Service (AKS) being one of the most popular managed options. AKS simplifies management by handling the control plane, but securing the environment remains the customer’s responsibility. The shared responsibility model requires you to focus on strengthening worker nodes, controlling cluster access, and ensuring that workloads and pods operate with the least privileges.&lt;br&gt;
Security in Kubernetes involves multiple layers. The base layer is the host security of the virtual machines in the node pools. Next is the cluster layer, where identity, networking, and governance must be carefully established and maintained. At the top, securing pods and containers that run your business logic is crucial to prevent privilege escalation or unauthorized communication. This approach, known as “defense in depth,” emphasizes addressing security across various boundaries instead of relying on a single tool or configuration for full protection.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Azure Kubernetes Chronicles 9: EKS in the Enterprise</title>
      <link>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-9-eks-in-the-enterprise/</link>
      <pubDate>Wed, 01 Oct 2025 07:47:46 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-9-eks-in-the-enterprise/</guid>
      <description>Why Amazon’s Kubernetes service is a compliance lever, not just duplication</description>
    </item>
    <item>
      <title>Azure Kubernetes Chronicles 8: Fleet in Focus</title>
      <link>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-8-fleet-in-focus/</link>
      <pubDate>Wed, 24 Sep 2025 11:36:24 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-8-fleet-in-focus/</guid>
      <description>Azure’s multi-cluster powerhouse — and where it falls short</description>
    </item>
    <item>
      <title>Azure Kubernetes Chronicles 7: The Multi-Cluster Reality</title>
      <link>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-7-the-multi-cluster-reality/</link>
      <pubDate>Thu, 18 Sep 2025 07:00:03 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-7-the-multi-cluster-reality/</guid>
      <description>From the dream of one perfect cluster to the messy truth of enterprise sprawl</description>
    </item>
    <item>
      <title>Azure Kubernetes Chronicles: Multi-Cluster Edition</title>
      <link>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-multi-cluster-edition/</link>
      <pubDate>Fri, 12 Sep 2025 08:01:27 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-multi-cluster-edition/</guid>
      <description>From Fleet to Edge — navigating Kubernetes across clouds and continents</description>
    </item>
    <item>
      <title>Azure Kubernetes Chronicles 6:</title>
      <link>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-6/</link>
      <pubDate>Wed, 03 Sep 2025 10:31:37 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-6/</guid>
      <description>Managing Multiple AKS Clusters with Azure Fleet</description>
    </item>
    <item>
      <title>Harnessing Chaos: Implementing Chaos Engineering with Azure Chaos Studio and Gremlin on AKS</title>
      <link>https://wolkwacht.nl/posts/harnessing-chaos-implementing-chaos-engineering-with-azure-chaos-studio-and-gremlin-on-aks/</link>
      <pubDate>Tue, 01 Jul 2025 12:42:28 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/harnessing-chaos-implementing-chaos-engineering-with-azure-chaos-studio-and-gremlin-on-aks/</guid>
      <description>Chaos Engineering is a crucial practice for modern cloud operations, enabling teams to identify hidden weaknesses and potential failures in…</description>
    </item>
    <item>
      <title>Azure Kubernetes Chronicles part 5:</title>
      <link>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-part-5/</link>
      <pubDate>Wed, 07 May 2025 06:53:40 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-part-5/</guid>
      <description>Autoscaling with KEDA</description>
    </item>
    <item>
      <title>Azure Kubernetes Chronicles part 4</title>
      <link>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-part-4/</link>
      <pubDate>Thu, 13 Mar 2025 10:41:00 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-part-4/</guid>
      <description>Dataprotection</description>
    </item>
    <item>
      <title>Azure Kubernetes Chronicles part 3</title>
      <link>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-part-3/</link>
      <pubDate>Fri, 28 Feb 2025 07:07:29 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-part-3/</guid>
      <description>Observability</description>
    </item>
    <item>
      <title>Azure Kubernetes Chronicles</title>
      <link>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-part-2/</link>
      <pubDate>Tue, 11 Feb 2025 09:17:00 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-part-2/</guid>
      <description>Networking using eBPF</description>
    </item>
    <item>
      <title>Azure Kubernetes Chronicles</title>
      <link>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-part-1/</link>
      <pubDate>Tue, 28 Jan 2025 08:05:02 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/azure-kubernetes-chronicles-part-1/</guid>
      <description>Container Network Interfaces</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>Kubernetes Community Days  Amsterdam 2023</title>
      <link>https://wolkwacht.nl/posts/kcd/</link>
      <pubDate>Wed, 01 Mar 2023 09:49:29 +0100</pubDate>
      <guid>https://wolkwacht.nl/posts/kcd/</guid>
      <description>Report of the Kubernetes Community Days Amsterdam 2023</description>
    </item>
    <item>
      <title>k3s: Enable Traefik dashboard</title>
      <link>https://wolkwacht.nl/posts/k3s-enable-traefik-dashboard/</link>
      <pubDate>Thu, 17 Oct 2019 10:37:20 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/k3s-enable-traefik-dashboard/</guid>
      <description>&lt;p&gt;If you install k3s with the default settings it also installs Traefik as a load balancer. Traefik also offers a dashboard which is very easy to enable. If you go on your k3s machines to the path /var/lib/rancher/k3s/server/manifests you can find their traefik.yaml. To enable the Traefik dashboard you have to add &lt;em&gt;dashboard.enabled: &amp;ldquo;true&amp;rdquo;&lt;/em&gt; to the yaml.&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;root@k3s-master-1:/var/lib/rancher/k3s/server/manifests# cat traefik.yaml
apiVersion: helm.cattle.io/v1
kind: HelmChart
metadata:
  name: traefik
  namespace: kube-system
spec:
  chart: https://%{KUBERNETES_API}%/static/charts/traefik-1.77.1.tgz
  set:
    rbac.enabled: &amp;#34;true&amp;#34;
    ssl.enabled: &amp;#34;true&amp;#34;
    metrics.prometheus.enabled: &amp;#34;true&amp;#34;
    kubernetes.ingressEndpoint.useDefaultPublishedService: &amp;#34;true&amp;#34;
    dashboard.enabled: &amp;#34;true&amp;#34;
root@k3s-master-1:/var/lib/rancher/k3s/server/manifests# cat traefik.yaml
apiVersion: helm.cattle.io/v1
kind: HelmChart
metadata:
  name: traefik
  namespace: kube-system
spec:
  chart: https://%{KUBERNETES_API}%/static/charts/traefik-1.77.1.tgz
  set:
    rbac.enabled: &amp;#34;true&amp;#34;
    ssl.enabled: &amp;#34;true&amp;#34;
    metrics.prometheus.enabled: &amp;#34;true&amp;#34;
    kubernetes.ingressEndpoint.useDefaultPublishedService: &amp;#34;true&amp;#34;
    dashboard.enabled: &amp;#34;true&amp;#34;
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;After a few minutes you will see some extra pods getting started.&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>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>
