DevSecOps Homelab Part 1: Introduction

Overview

Alright, let's kick things off with the first of a three-part series where I share my latest pet project: tinkering with DevSecOps concepts in my homelab. In this article, I'll dive into the nitty-gritty – what's up with this project, and why am I even bothering with it?

What is a homelab?

First, we need to understand what a homelab is. Simply put, a homelab is a dedicated space where individuals can experiment, learn, and practice various concepts of IT, networking, cybersecurity, or other related fields, in a controlled environment.

Homelabs typically consists of physical hardware such as servers, switches, and routers, as well as virtualized environments using virtualization software like VMware or VirtualBox. In my case, I rely on virtualization for now as investing in physical hardware isn't feasible at the moment.

Why bother building a homelab?

Aside from the reasons mentioned above, they offer a prime opportunity to showcase your skills and knowledge to potential employers. Additionally, having a homelab demonstrates initiative and a genuine passion for your field. It shows that you're not content to just learn in a classroom or office setting—you're actively seeking out opportunities to expand your skills and knowledge on your own time.

So, yeah, that's my main motivation for undertaking this project, it's to level-up my DevSecOps game, feed my curiosity, and have tons of fun along the way!

Alright, what's up next?

Well, I'm not gonna tell you how to build your own virtual homelab. That's been covered extensively in other tutorials. Instead, in the next article, we're rolling up our sleeves and jumping straight into setting up the CI/CD pipeline. Keep an eye out for it!