How killerlux/cloudprojet works
Project Type & Purpose
• A Kubernetes-based “cloud migration” lab: uses Vagrant to spin up a 2-node local K8s cluster (1 master, 1 worker) and deploys Nginx plus Odoo + PostgreSQL via YAML manifests.
Main Components
• Host machine: runs Vagrant/VirtualBox
• Vagrant infra:
– Vagrantfile + setup scripts → provisions k8s-master & k8s-worker01
• Kubernetes cluster:
– Control plane (kube-apiserver, etcd, scheduler) on master
– Worker node (kubelet, kube-proxy) with hostPath PV on /mnt/data-postgres-pv
• Applications (in namespace clay-technology-prod):
– Nginx Deployment + Service
– Odoo + PostgreSQL (ConfigMap, PV/PVC, Deployments, Services)
Relationships & Data Flows
• Vagrantfile → triggers master-setup.sh → initializes kubeadm control-plane
• kubeadm join → worker registers with master
• kubectl apply (namespace, apps) → API server → etcd → scheduler → kubelets
• User HTTP traffic → NodePort on worker → Service → Pod
Architectural Patterns & Technologies
• Immutable infra as code (Vagrant + shell scripts)
• Kubernetes control-plane/worker separation
• HostPath PersistentVolume for PostgreSQL
• Namespaced deployments for isolation
• YAML manifests for declarative deployments