<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cdk8s on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/cdk8s/</link>
    <description>Recent content in Cdk8s on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 16 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/cdk8s/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Kubernetes Resource Templates: cdk8s vs Jsonnet vs KCL</title>
      <link>https://www.pistack.xyz/posts/2026-05-16-kubernetes-resource-templates-cdk8s-jsonnet-kcl/</link>
      <pubDate>Sat, 16 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-16-kubernetes-resource-templates-cdk8s-jsonnet-kcl/</guid>
      <description>&lt;p&gt;Managing Kubernetes manifests at scale is one of the most common pain points for platform engineering teams. Raw YAML files quickly become unmanageable as the number of deployments grows — duplication, inconsistent labeling, and configuration drift are inevitable without a templating strategy.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
