<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Husna Hariz on Caktus Group</title><link>https://www.caktusgroup.com/authors/husna-hariz/</link><description>Recent content in Husna Hariz on Caktus Group</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 24 Sep 2025 22:18:00 +0300</lastBuildDate><atom:link href="https://www.caktusgroup.com/authors/husna-hariz/index.xml" rel="self" type="application/rss+xml"/><item><title>Migrating Amazon EKS Nodes to Amazon Linux 2023 (AL2023) from Amazon Linux 2 (AL2) Using CloudFormation and Troposphere</title><link>https://www.caktusgroup.com/blog/2025/09/migrate-eks-nodes-from-al2-to-al2023-images/</link><pubDate>Wed, 24 Sep 2025 22:18:00 +0300</pubDate><guid>https://www.caktusgroup.com/blog/2025/09/migrate-eks-nodes-from-al2-to-al2023-images/</guid><description>&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>In this post, we’ll explain how we extended our existing AWS CloudFormation infrastructure, built using &lt;a href="https://github.com/cloudtools/troposphere" target="_blank" rel="noopener noreferrer">Troposphere&lt;/a>, to support the use of &lt;code>Amazon Linux 2023 (AL2023)&lt;/code> for Amazon EKS (Elastic Kubernetes Service) nodes. This migration was necessary to ensure compatibility ahead of our planned upgrade to &lt;code>Kubernetes version 1.33&lt;/code>.&lt;/p></description></item></channel></rss>