<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Github-Actions on Apurv Kiri | Tech Notes</title>
    <link>https://apurv.me/tags/github-actions/</link>
    <description>Recent content in Github-Actions on Apurv Kiri | Tech Notes</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Wed, 28 Oct 2026 01:55:15 +0530</lastBuildDate><atom:link href="https://apurv.me/tags/github-actions/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes - Automated Dependency Updates with Renovate</title>
      <link>https://apurv.me/posts/kubernetes-automated-dependency-updates-with-renovate/</link>
      <pubDate>Wed, 28 Oct 2026 01:55:15 +0530</pubDate>
      
      <guid>https://apurv.me/posts/kubernetes-automated-dependency-updates-with-renovate/</guid>
      
      <description>&lt;hr&gt;
&lt;p&gt;This post is part of our ongoing series of posts for Kubernetes. In this post, we will automate dependency updates for our GitOps repository using &lt;strong&gt;Renovate&lt;/strong&gt;, an open-source tool that finds outdated dependencies and raises pull requests to update them.&lt;/p&gt;
&lt;p&gt;All components in our cluster are pinned to a specific version: Helm charts in &lt;code&gt;HelmRelease&lt;/code&gt;, Flux itself in &lt;code&gt;gotk-components.yaml&lt;/code&gt;, and actions in our GitHub workflows. This is what GitOps expects, but nothing tells us when these versions become outdated. We hadn&amp;rsquo;t touched our cluster for a while, and by the time we came back, every Helm chart had a newer release available. Checking release pages manually for each of them is error-prone and time-consuming.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
