diff --git a/content/blog/docker-deep-dive.md b/content/blog/docker-deep-dive.md
index a072423..7acbc14 100644
--- a/content/blog/docker-deep-dive.md
+++ b/content/blog/docker-deep-dive.md
@@ -5,6 +5,7 @@ date: 2024-04-24
draft: false
featured: true
weight: 1
+tags: ["docker", "containers"]
---
@@ -160,4 +161,4 @@ By understanding Docker licensing and ensuring that your usage complies with the
### Conclusion
-To wrap up, getting the hang of Docker is about more than just wrapping your app in a container. It’s about really getting into the nitty-gritty—like setting up Dockerfiles properly, making smart use of Docker’s caching perks, and keeping those images lean and mean. On top of that, keeping things above board with Docker’s licensing rules is key for keeping your operations smooth and compliant. Stick with these strategies, and you’re on your way to making your Docker setups as efficient, secure, and compliant as they can be.
\ No newline at end of file
+To wrap up, getting the hang of Docker is about more than just wrapping your app in a container. It’s about really getting into the nitty-gritty—like setting up Dockerfiles properly, making smart use of Docker’s caching perks, and keeping those images lean and mean. On top of that, keeping things above board with Docker’s licensing rules is key for keeping your operations smooth and compliant. Stick with these strategies, and you’re on your way to making your Docker setups as efficient, secure, and compliant as they can be.
diff --git a/content/blog/genai-dictionary-part1-llm.md b/content/blog/genai-dictionary-part1-llm.md
index 94a825e..e6bd7f8 100644
--- a/content/blog/genai-dictionary-part1-llm.md
+++ b/content/blog/genai-dictionary-part1-llm.md
@@ -8,6 +8,7 @@ weight: 1
sitemap:
changefreq: "monthly"
priority: 1
+tags: ["genai", "llm", "ai"]
---
We bring to you this weekly series of articles, to help understand and demystify the lexicon in the GenAI space.
diff --git a/content/blog/github-runners.md b/content/blog/github-runners.md
index 1f48a19..5092c2b 100644
--- a/content/blog/github-runners.md
+++ b/content/blog/github-runners.md
@@ -5,6 +5,7 @@ date: 2024-04-25
draft: false
featured: true
weight: 1
+tags: ["github", "ci-cd", "automation"]
---
# Introduction
@@ -162,4 +163,4 @@ GitHub automatically sends notifications about CI/CD workflow status updates to
GitHub Runners are the backbone of modern CI/CD pipelines, enabling developers to automate their workflows with ease and efficiency. Whether you opt for GitHub-hosted runners for convenience or self-hosted runners for control, GitHub provides the tools and infrastructure to support your automation needs.
-By embracing GitHub Runners, you can unlock new levels of productivity and innovation, allowing your projects to reach their full potential. So, don't wait any longer! Dive into the world of GitHub Runners and elevate your CI/CD workflow today!
\ No newline at end of file
+By embracing GitHub Runners, you can unlock new levels of productivity and innovation, allowing your projects to reach their full potential. So, don't wait any longer! Dive into the world of GitHub Runners and elevate your CI/CD workflow today!
diff --git a/content/blog/guide-to-implement-winston-logger.md b/content/blog/guide-to-implement-winston-logger.md
index f4f7f67..b5dd47f 100644
--- a/content/blog/guide-to-implement-winston-logger.md
+++ b/content/blog/guide-to-implement-winston-logger.md
@@ -5,6 +5,7 @@ date: 2024-04-29
draft: false
featured: true
weight: 1
+tags: ["nodejs", "logging", "winston"]
---
___
@@ -294,4 +295,4 @@ transports: [
In this step-by-step guide, we've explored the implementation of Winston Logger in Node.js projects, enabling us to build robust and reliable applications. With best practices like utilizing log levels, including contextual information, and centralizing logging configuration, we've paved the way for more reliable and usable Node.js applications.
-Let's embark on our logging journey to enhance our projects further!!
\ No newline at end of file
+Let's embark on our logging journey to enhance our projects further!!
diff --git a/content/blog/header-Based-traffic-routing-using-argo-rollouts.md b/content/blog/header-Based-traffic-routing-using-argo-rollouts.md
index 9cff9c3..8bd113c 100644
--- a/content/blog/header-Based-traffic-routing-using-argo-rollouts.md
+++ b/content/blog/header-Based-traffic-routing-using-argo-rollouts.md
@@ -5,6 +5,7 @@ date: 2024-05-27
draft: false
featured: true
weight: 1
+tags: ["argo", "kubernetes", "traffic-routing"]
---
This blog explores how to use Argo Rollouts for deploying software updates smoothly. It covers the challenges faced when rolling back updates and introduces header-based routing to manage traffic during deployments.
diff --git a/content/blog/hive-to-unity-catalog-data-migration-databricks.md b/content/blog/hive-to-unity-catalog-data-migration-databricks.md
index 02617e2..f964b7c 100644
--- a/content/blog/hive-to-unity-catalog-data-migration-databricks.md
+++ b/content/blog/hive-to-unity-catalog-data-migration-databricks.md
@@ -5,6 +5,7 @@ date: 2024-11-09
draft: false
featured: true
weight: 1
+tags: ["databricks", "hive", "unity-catalog", "data-migration"]
---
diff --git a/content/blog/is-dns-migration-a-tricky-affair.md b/content/blog/is-dns-migration-a-tricky-affair.md
index 11a3fe3..b2f38d0 100644
--- a/content/blog/is-dns-migration-a-tricky-affair.md
+++ b/content/blog/is-dns-migration-a-tricky-affair.md
@@ -5,6 +5,7 @@ date: 2022-12-15
draft: false
featured: true
weight: 1
+tags: ["dns", "migration"]
---
Never trust a friend who says DNS migration is easy. Your instinct says it's easy, well don't trust your instinct. In this post, I will be sharing my experience with one such encounter with DNS migration from GoDaddy to Route53.
diff --git a/content/blog/java-streams.md b/content/blog/java-streams.md
index 596224c..5a1ae45 100644
--- a/content/blog/java-streams.md
+++ b/content/blog/java-streams.md
@@ -5,6 +5,7 @@ date: 2024-03-05
draft: false
featured: true
weight: 1
+tags: ["java", "streams"]
---
# Java Streams: A Paradigm Shift in Data Processing
diff --git a/content/blog/kubernetes-rbac.md b/content/blog/kubernetes-rbac.md
index 3921cb4..896bef0 100644
--- a/content/blog/kubernetes-rbac.md
+++ b/content/blog/kubernetes-rbac.md
@@ -5,6 +5,7 @@ date: 2024-04-29
draft: false
featured: true
weight: 1
+tags: ["kubernetes", "rbac", "security"]
---
Role-Based Access Control (RBAC) is a crucial feature in Kubernetes that allows administrators to define and manage permissions for users and services within the cluster. RBAC helps prevent unauthorised access and actions, ensuring the security of your Kubernetes environment. In this blog, we'll explore how RBAC works in Kubernetes, its components, and best practices.
diff --git a/content/blog/lightweight-k3s-cluster-raspberry-pi.md b/content/blog/lightweight-k3s-cluster-raspberry-pi.md
index 95a84e5..eaac3e1 100644
--- a/content/blog/lightweight-k3s-cluster-raspberry-pi.md
+++ b/content/blog/lightweight-k3s-cluster-raspberry-pi.md
@@ -5,6 +5,7 @@ date: 2023-01-02
draft: false
featured: true
weight: 1
+tags: ["k3s", "kubernetes", "raspberry-pi", "iot"]
---
As a developer at Infraspec, I am responsible for managing internal tooling and ensuring the smooth operation of local
tooling and network services in our office. We had a cluster of Raspberry Pi devices available and saw an opportunity to
diff --git a/content/blog/linux-memory-swap.md b/content/blog/linux-memory-swap.md
index 4d522a2..ca58b76 100644
--- a/content/blog/linux-memory-swap.md
+++ b/content/blog/linux-memory-swap.md
@@ -5,6 +5,7 @@ date: 2024-04-15
draft: false
featured: true
weight: 1
+tags: ["linux", "memory", "swap"]
---
diff --git a/content/blog/multi-tenant-system-with-aws-cdk.md b/content/blog/multi-tenant-system-with-aws-cdk.md
index 21747d2..84bcc13 100644
--- a/content/blog/multi-tenant-system-with-aws-cdk.md
+++ b/content/blog/multi-tenant-system-with-aws-cdk.md
@@ -5,6 +5,7 @@ date: 2024-11-22
draft: false
featured: true
weight: 1
+tags: ["aws", "cdk", "multi-tenancy"]
---
In this blog, I will be taking you on a journey of building the scalable and efficient IAC solution that we build for our multi-tenant system. Here we are not going to debate why we chose the CDK; that will be another discussion that can be highlighted in another blog. Instead, how we approached solving using AWS CDK is going to be discussed in this blog. Even if you are not very familiar with CDK, this blog can help to build a mental model of how we can think while writing the code for the infrastructure of such a complex system.
diff --git a/content/blog/nfs-fs-as-docker-volume.md b/content/blog/nfs-fs-as-docker-volume.md
index d28b1b1..8722235 100644
--- a/content/blog/nfs-fs-as-docker-volume.md
+++ b/content/blog/nfs-fs-as-docker-volume.md
@@ -5,6 +5,7 @@ date: 2024-08-19
draft: false
featured: true
weight: 1
+tags: ["docker", "nfs", "storage"]
---
As an Infrastructure engineer, I've had my fair share of experiences with containerized environments and the challenges of managing data persistence. One of the most significant problems I've faced is ensuring that data generated by Docker containers persists even when the container is stopped or deleted. That's when I discovered the power of leveraging the Network File System (NFS) as volumes in Docker.
diff --git a/content/blog/office-home-lab-internet-failover-setup.md b/content/blog/office-home-lab-internet-failover-setup.md
index 886bf18..e0494a0 100644
--- a/content/blog/office-home-lab-internet-failover-setup.md
+++ b/content/blog/office-home-lab-internet-failover-setup.md
@@ -5,6 +5,7 @@ date: 2022-12-15
draft: false
featured: true
weight: 1
+tags: ["networking", "home-lab", "failover"]
---
An overview of how to set up internet failover for an office or home lab.
diff --git a/content/blog/pragmatism-over-perfection.md b/content/blog/pragmatism-over-perfection.md
index aa146d6..d65c6c0 100644
--- a/content/blog/pragmatism-over-perfection.md
+++ b/content/blog/pragmatism-over-perfection.md
@@ -5,6 +5,7 @@ date: 2025-04-21
draft: false
featured: true
weight: 1
+tags: ["software-development", "philosophy"]
---
We as Engineers often chase perfection.
diff --git a/content/blog/rpi-netboot-automation.md b/content/blog/rpi-netboot-automation.md
index 1dbac29..80e78e2 100644
--- a/content/blog/rpi-netboot-automation.md
+++ b/content/blog/rpi-netboot-automation.md
@@ -5,6 +5,7 @@ date: 2024-04-17
draft: false
featured: true
weight: 1
+tags: ["raspberry-pi", "netboot", "automation"]
---
In this blog, we'll delve into automating the netbooting process using a bash script (`pxeService.sh`) and an address list (`addresslist.txt`) to enhance the deployment and management of Raspberry Pi devices. If you haven't already, you can catch up on the initial steps and concepts discussed [here](https://www.infraspec.dev/blog/rpi-netboot-deep-dive/), where we laid the groundwork for this automation project.
diff --git a/content/blog/rpi-netboot-deep-dive.md b/content/blog/rpi-netboot-deep-dive.md
index 94edab1..44d1628 100644
--- a/content/blog/rpi-netboot-deep-dive.md
+++ b/content/blog/rpi-netboot-deep-dive.md
@@ -5,6 +5,7 @@ date: 2024-04-16
draft: false
featured: true
weight: 1
+tags: ["raspberry-pi", "netboot", "automation"]
---
## Understanding PXE Boot
diff --git a/content/blog/securing-and-rotating-secrets-with-aws-secrets-manager-part-1.md b/content/blog/securing-and-rotating-secrets-with-aws-secrets-manager-part-1.md
index 8ea4d9c..068a292 100644
--- a/content/blog/securing-and-rotating-secrets-with-aws-secrets-manager-part-1.md
+++ b/content/blog/securing-and-rotating-secrets-with-aws-secrets-manager-part-1.md
@@ -5,6 +5,7 @@ date: 2024-04-21
draft: false
featured: true
weight: 1
+tags: ["aws", "secrets-manager", "security"]
---
Automating Secret Rotation with AWS Secrets Manager
diff --git a/content/blog/securing-and-rotating-secrets-with-aws-secrets-manager-part-2.md b/content/blog/securing-and-rotating-secrets-with-aws-secrets-manager-part-2.md
index a809aaf..2e4e5ab 100644
--- a/content/blog/securing-and-rotating-secrets-with-aws-secrets-manager-part-2.md
+++ b/content/blog/securing-and-rotating-secrets-with-aws-secrets-manager-part-2.md
@@ -5,6 +5,7 @@ date: 2024-04-22
draft: false
featured: true
weight: 1
+tags: ["aws", "secrets-manager", "security"]
---
In [Part 1](/blog/securing-and-rotating-secrets-with-aws-secrets-manager-part-1/), we discussed upon configuring AWS Secrets Manager, AWS Lambda, and Automatic Rotation for our Secret. We also defined permissions for our Lambda function, which enabled the Secrets Manager to invoke it on a scheduled basis. In Part 2, we will focus on setting up the Lambda function, including the required permissions and implementation.
diff --git a/content/blog/setting-up-ingress-on-eks.md b/content/blog/setting-up-ingress-on-eks.md
index 2ba4cb9..161f43a 100644
--- a/content/blog/setting-up-ingress-on-eks.md
+++ b/content/blog/setting-up-ingress-on-eks.md
@@ -5,6 +5,7 @@ date: 2022-11-30
draft: false
featured: true
weight: 1
+tags: ["aws", "eks", "kubernetes", "ingress"]
---
> **Note**: Everything here applies to [Amazon Elastic Kubernetes Service (EKS)](https://aws.amazon.com/eks/). If you are running on another cloud, on-prem, with minikube, or something else, these will be slightly different.
diff --git a/content/blog/tag-strat-blog.md b/content/blog/tag-strat-blog.md
index 6c0e181..ba0709d 100644
--- a/content/blog/tag-strat-blog.md
+++ b/content/blog/tag-strat-blog.md
@@ -5,6 +5,7 @@ date: 2024-07-29
draft: false
featured: true
weight: 1
+tags: ["aws", "tagging", "strategy"]
---
## Introduction
diff --git a/content/blog/tdd-design-benefits.md b/content/blog/tdd-design-benefits.md
index 97e841f..25eb26b 100644
--- a/content/blog/tdd-design-benefits.md
+++ b/content/blog/tdd-design-benefits.md
@@ -5,6 +5,7 @@ date: 2023-01-18
draft: false
featured: true
weight: 1
+tags: ["tdd", "software-design"]
---
Most of us think of TDD as a tool for software testing and verification. But if used effectively it is more than that.
diff --git a/content/blog/terraform_secrets_management_guide.md b/content/blog/terraform_secrets_management_guide.md
index 493c187..bbc6317 100644
--- a/content/blog/terraform_secrets_management_guide.md
+++ b/content/blog/terraform_secrets_management_guide.md
@@ -5,6 +5,7 @@ date: 2024-08-06
draft: false
featured: true
weight: 1
+tags: ["terraform", "aws", "secrets-management"]
---
Imagine you're working on a project where you need to deploy resources to aws using terraform. In a rush to get things done, you decide to hard-code your AWS credentials directly into your Terraform files. Everything works fine at first, and your resources are successfully deployed. But a few weeks later, you discover that your Terraform repository was accidentally made public. Suddenly, your AWS credentials are exposed to the entire internet. Exposing your credentials can lead to unauthorized access to your AWS account, leading to serious security problems.
diff --git a/content/blog/terragrunt-envs-management.md b/content/blog/terragrunt-envs-management.md
index adfeb9b..a6e6fe6 100644
--- a/content/blog/terragrunt-envs-management.md
+++ b/content/blog/terragrunt-envs-management.md
@@ -5,6 +5,7 @@ date: 2024-09-10
draft: false
featured: true
weight: 1
+tags: ["terragrunt", "terraform", "iac"]
---
Managing multiple environments was a never-ending headache for me. Like many others in the DevOps world, I was responsible for deploying applications across various environments—production, staging, and development. Each of these environments required the same infrastructure, but I found myself writing the same Terraform code over and over again in different folders. The repetition felt inefficient, and the potential for human error only grew with each tweak I had to make for a specific environment.
diff --git a/content/blog/tftp-overview.md b/content/blog/tftp-overview.md
index 0923c8e..832c818 100644
--- a/content/blog/tftp-overview.md
+++ b/content/blog/tftp-overview.md
@@ -5,6 +5,7 @@ date: 2024-04-19
draft: false
featured: true
weight: 1
+tags: ["tftp", "networking"]
---
## TFTP protocol overview
diff --git a/hugo.log b/hugo.log
new file mode 100644
index 0000000..5e326f7
--- /dev/null
+++ b/hugo.log
@@ -0,0 +1,5 @@
+port 1313 already in use, attempting to use an available port
+Watching for changes in /app/{assets,content,data,layouts,static}
+Watching for config changes in /app/config.toml
+Start building sites …
+hugo v0.150.1-ce44a8e835e6934292acda936e5b43b70f451af9+extended linux/amd64 BuildDate=2025-09-25T10:26:04Z VendorInfo=gohugoio
diff --git a/layouts/blog/list.html b/layouts/blog/list.html
index 2ded97d..49457fc 100644
--- a/layouts/blog/list.html
+++ b/layouts/blog/list.html
@@ -10,10 +10,44 @@
{{ .Summary }}
+