<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on Humayun Manzer</title><link>https://humayunhub.com/blog/</link><description>Recent content in Blog on Humayun Manzer</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 24 Aug 2025 23:05:00 +0800</lastBuildDate><atom:link href="https://humayunhub.com/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Chaos Engineering in Small Teams: Worth It or Overkill?</title><link>https://humayunhub.com/blog/2025/chaosengineering/</link><pubDate>Sun, 24 Aug 2025 23:05:00 +0800</pubDate><guid>https://humayunhub.com/blog/2025/chaosengineering/</guid><description>&lt;div class="paragraph">

 &lt;small>&lt;i>&lt;a href="https://unsplash.com/photos/blue-and-green-peacock-feather-58Z17lnVS4U?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>Netflix made Chaos Engineering famous with Chaos Monkey, but what about small teams with only a few engineers? Is it practical, or just a distraction when you’ve already got your hands full with CI/CD, monitoring, and on-call? Here’s a grounded look at when it makes sense and how to keep it lightweight.&lt;/p>
&lt;/div>
&lt;div class="paragraph">
&lt;p>Chaos Engineering is about introducing controlled failures to expose weaknesses before they show up in production. Examples: killing pods, injecting latency, simulating node crashes. For tech giants with hundreds of services, it’s a must. For smaller teams, the question is whether the effort pays off.&lt;/p>
&lt;/div></description></item><item><title>Terraform count vs for_each: A Friendly Guide (+ Cheatsheet)</title><link>https://humayunhub.com/blog/2025/terraform_count_foreach/</link><pubDate>Wed, 23 Jul 2025 18:00:00 +0800</pubDate><guid>https://humayunhub.com/blog/2025/terraform_count_foreach/</guid><description>&lt;div class="paragraph">

 &lt;small>&lt;i>&lt;a href="https://unsplash.com/photos/a-couple-of-toy-cars-sitting-on-top-of-a-table-3pxbdA4XGFQ?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>Choosing between &lt;code>count&lt;/code> and &lt;code>for_each&lt;/code> in Terraform looks simple at first, but it can change how predictable your infrastructure is over time. I’ve been bitten by both approaches in the past, so here’s a practical guide to when each one makes sense, with examples and a quick cheatsheet.&lt;/p>
&lt;/div></description></item><item><title>Secure SDLC</title><link>https://humayunhub.com/blog/2025/securesdlc/</link><pubDate>Mon, 23 Jun 2025 18:00:00 +0800</pubDate><guid>https://humayunhub.com/blog/2025/securesdlc/</guid><description>&lt;div class="paragraph">

 &lt;small>&lt;i>&lt;a href="https://unsplash.com/photos/grey-metal-chain-link-fence-ZLfl16yNSTY?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>In today’s fast-paced software development landscape, security can no longer be an afterthought. The traditional Software Development Life Cycle (SDLC) often treated security as a final step, a gate that developers had to pass through before deployment. This approach led to vulnerabilities slipping through the cracks, resulting in costly breaches and reputational damages.
Instead, we need to embrace a Secure SDLC (SSDLC) that integrates security into every phase of development. This is where DevSecOps comes in.&lt;/p>
&lt;/div></description></item><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><item><title>Bash to Powershell Cheatsheet</title><link>https://humayunhub.com/blog/2025/bashtopowershell/</link><pubDate>Tue, 10 Jun 2025 16:00:00 +0800</pubDate><guid>https://humayunhub.com/blog/2025/bashtopowershell/</guid><description>&lt;div class="paragraph">

 &lt;small>&lt;i>&lt;a href="https://unsplash.com/photos/persons-hand-on-white-wall-36g19a7ivrs">Photo credit&lt;/a>&lt;/i>&lt;/small>

&lt;/div>
&lt;div class="paragraph">
&lt;p>Bash to PowerShell Cheatsheet: A quick reference guide to help you translate common Bash commands into their PowerShell equivalents—and vice versa.&lt;/p>
&lt;/div>
&lt;div class="paragraph">
&lt;p>Ideal for developers, sysadmins, or anyone transitioning between Linux and Windows environments.&lt;/p>
&lt;/div></description></item><item><title>Common Issues Faced in DevOps</title><link>https://humayunhub.com/blog/2025/commondevopsissues/</link><pubDate>Thu, 05 Jun 2025 18:50:06 +0800</pubDate><guid>https://humayunhub.com/blog/2025/commondevopsissues/</guid><description>&lt;div class="paragraph">
&lt;p>I recently had a few hiccups while dealing with our DevOps Pipeline.&lt;/p>
&lt;/div>
&lt;div class="paragraph">
&lt;p>This blog post will hopefully help you understand, the common issues that we deal with DevOps pipeline.&lt;/p>
&lt;/div></description></item></channel></rss>