<?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>Cue on Software Engineer - Jinsu Park</title><link>https://umi0410.github.io/en/tags/cue/</link><description>Recent content in Cue on Software Engineer - Jinsu Park</description><generator>Hugo -- 0.150.1</generator><language>en</language><lastBuildDate>Mon, 15 Jun 2026 00:00:00 +0900</lastBuildDate><atom:link href="https://umi0410.github.io/en/tags/cue/index.xml" rel="self" type="application/rss+xml"/><item><title>Stop Struggling With Helm Charts: Author Kubernetes Manifests with CUE</title><link>https://umi0410.github.io/en/blog/devops/kubernetes-manifests-with-cue/</link><pubDate>Mon, 15 Jun 2026 00:00:00 +0900</pubDate><guid>https://umi0410.github.io/en/blog/devops/kubernetes-manifests-with-cue/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Part 1 of a series on managing Kubernetes configuration at scale.
Upcoming: comparing CUE and Helm for different use cases, and integrating CUE into CI/CD pipelines and GitOps workflows.&lt;/p&gt;&lt;/blockquote&gt;
&lt;hr&gt;
&lt;p&gt;I have spent the past four years as a DevOps engineer reading, using, and writing Helm charts — from small internal deployment wrappers to large, multi-team platform charts. I have read through the internals of charts for Istio, CockroachDB, ArgoCD, cert-manager, and Vault, and written enough &lt;code&gt;_helpers.tpl&lt;/code&gt; macros and validations to last a lifetime.&lt;/p&gt;</description></item></channel></rss>