<?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>Workload Identity on Wolkwacht</title>
    <link>https://wolkwacht.nl/tags/workload-identity/</link>
    <description>Recent content in Workload Identity 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>Wed, 21 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://wolkwacht.nl/tags/workload-identity/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Securing and Scaling Dapr for Production on AKS</title>
      <link>https://wolkwacht.nl/posts/securing-and-scaling-dapr-for-production-on-aks/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/securing-and-scaling-dapr-for-production-on-aks/</guid>
      <description>&lt;p&gt;&lt;img alt=&#34;Dapr-enabled application pods protected by identity and policy while scaling across AKS nodes&#34; loading=&#34;lazy&#34; src=&#34;https://wolkwacht.nl/images/2026/dapr-security-scaling-feature.svg&#34;&gt;&lt;/p&gt;
&lt;p&gt;A Dapr-enabled application can work perfectly with one replica and still be unprepared for production. The sidecar may have no resource requests, every application may be able to load every component, a rollout may require capacity the cluster does not have, or an autoscaler may react to application CPU while ignoring a throttled &lt;code&gt;daprd&lt;/code&gt; container.&lt;/p&gt;
&lt;p&gt;Production readiness is therefore not one switch. It is a chain of explicit decisions about identity, authorization, isolation, capacity, rollout behaviour, scaling signals, and control-plane availability.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
