<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubernetes on Humayun Manzer</title><link>https://humayunhub.com/tags/kubernetes/</link><description>Recent content in Kubernetes on Humayun Manzer</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 22 Jun 2025 17:28:00 +0800</lastBuildDate><atom:link href="https://humayunhub.com/tags/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>Secure Secret Management in Kubernetes</title><link>https://humayunhub.com/blog/2025/securesecrets/</link><pubDate>Sun, 22 Jun 2025 17:28:00 +0800</pubDate><guid>https://humayunhub.com/blog/2025/securesecrets/</guid><description>&lt;div class="paragraph">

 &lt;small>&lt;i>&lt;a href="https://unsplash.com/photos/opened-secret-door-inside-library-HK8IoD-5zpg?utm_content=creditShareLink&amp;amp;utm_medium=referral&amp;amp;utm_source=unsplash">Photo credit&lt;/a>&lt;/i>&lt;/small>

&lt;/div>
&lt;div class="paragraph">
&lt;p>Effectively managing sensitive information such as API keys, passwords, and certificates within a Kubernetes environment and ensuring that this data remains inaccessible to cluster administrators or system operators is a critical requirement for organizations that prioritize strong security and compliance.&lt;/p>
&lt;/div>
&lt;div class="paragraph">
&lt;p>To achieve this level of protection, especially in multi-tenant or regulated environments, several robust strategies and tools can be employed to minimize the risk of unauthorized access to secrets.&lt;/p>
&lt;/div>
&lt;div class="paragraph">
&lt;p>Following are some of the best practices and methods to secure secrets in Kubernetes, ensuring that they are not visible to administrators or operators:&lt;/p>
&lt;/div></description></item><item><title>Karpenter in AWS</title><link>https://humayunhub.com/blog/2025/karpenter/</link><pubDate>Sat, 14 Jun 2025 19:58:00 +0800</pubDate><guid>https://humayunhub.com/blog/2025/karpenter/</guid><description>&lt;div class="paragraph">
&lt;p>Karpenter is an open-source Kubernetes node autoscaler developed by AWS. It automatically launches the right compute resources (EC2 instances) when your cluster needs them and shuts them down when they’re no longer needed.&lt;/p>
&lt;/div>
&lt;div class="paragraph">
&lt;p>Traditional autoscalers (like the Cluster Autoscaler) work well but can be slow and limited in flexibility. Karpenter is designed to be:&lt;/p>
&lt;/div>
&lt;div class="paragraph">
&lt;p>Faster: It reacts quickly to unschedulable pods.
Smarter: It chooses the best instance types based on your workload needs.
Cost-efficient: It can use spot instances and right-size nodes to save money.
Flexible: It doesn’t require pre-defined node groups.&lt;/p>
&lt;/div></description></item></channel></rss>