<?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>Dapr on Wolkwacht</title>
    <link>https://wolkwacht.nl/topics/dapr/</link>
    <description>Recent content in Dapr 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/topics/dapr/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>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>
  </channel>
</rss>
