Back to projects

42 project

Inception of Things

A DevOps infrastructure project focused on Vagrant, K3s, Kubernetes and GitOps deployment with Argo CD.

Stack

  • Kubernetes
  • K3s
  • Vagrant
  • Argo CD
  • Docker
  • YAML
  • Ingress
  • Linux

Skills gained

  • Provisioning reproducible virtual machines with Vagrant
  • Deploying and configuring a lightweight Kubernetes cluster with K3s
  • Understanding pods, services, deployments, ingress and namespaces
  • Using Argo CD to deploy and synchronize applications from Git
  • Automating infrastructure setup with Shell scripts
  • Debugging networking, routing and service exposure inside a local cluster

Links

Inception of Things is a DevOps-oriented 42 project built around local infrastructure, Kubernetes and GitOps. The goal was to provision virtual machines with Vagrant, deploy a lightweight K3s cluster, expose services properly and use Argo CD to synchronize an application from a Git repository. It made infrastructure feel less abstract and much more concrete.

01 — Provisioning

A local cluster from scratch.

The project starts with Vagrant. Each machine is described, provisioned and configured from scripts, so the environment can be rebuilt cleanly instead of relying on manual setup. It is a good introduction to infrastructure as something you define, not something you click together once and hope never breaks.

Humorous illustration of a local infrastructure setup with several virtual machines
Fig. 01
When your laptop turns into a tiny datacenter and starts sounding like an airplane.

02 — Kubernetes

Kubernetes, but lighter.

K3s brings Kubernetes into the project without the weight of a full production cluster. Pods, services, deployments and ingress become easier to understand once they run on your own machines. The project makes orchestration concrete: describe the desired state, expose the right services, then debug what actually happens.

Humorous illustration of Kubernetes orchestrating multiple services
Fig. 02
Kubernetes: a lot of YAML to basically say “run this thing and keep it alive”.

03 — GitOps

Argo CD does the syncing.

The final part introduces Argo CD and the GitOps workflow. Instead of manually deploying an application, the cluster watches a Git repository and synchronizes the desired state from it. This makes deployments easier to track, easier to reproduce and much closer to how modern infrastructure is managed.

Humorous illustration of Argo CD synchronizing an application from Git to Kubernetes
Fig. 03
Push to Git, wait a bit, pretend you did not spend an hour debugging YAML indentation.
Back to projects