lab

the home lab, documented and measured — the tracker records intent, the snapshot records reality.

live snapshot

probed 2026-11-17 (0h ago)

cluster

kind-lab

carried forward — k8s v1.37.0 · control-plane ready

pods

32 / 34 ready

616 restarts (lifetime)

forge

down

https://forge.lab.local/

vms

none up

ssh fwd loopback / loopback

deployments

argocdargocd-applicationset-controller1/1
argocdargocd-dex-server1/1
argocdargocd-notifications-controller1/1
argocdargocd-redis1/1
argocdargocd-repo-server1/1
argocdargocd-server1/1
cert-managercert-manager1/1
cert-managercert-manager-cainjector1/1
cert-managercert-manager-webhook1/1
forgejoforgejo1/1
forgejoforgejo-docs1/1
forgejoforgejo-registry1/1
forgejoforgejo-runner1/1
forgejoforgejo-truthguard-metrics1/1
ingress-nginxingress-nginx-controller1/1
kube-systemcoredns2/2
kube-systemmetrics-server1/1
local-path-storagelocal-path-provisioner1/1
observegrafana1/1
observekube-state-metrics1/1
observepostgres-exporter1/1
observeprometheus1/1
three-tiersapi0/0
three-tierspg1/1
three-tiersweb1/1

control-plane: cpu 357m · mem 2368Mi

the network, in one glance

kind nodeone control-plane node · api and nodeport unpublished from the internet
three-tiersweb published to the host only · api + postgres clusterip only (deliberately unpublished)
observeprometheus · grafana · kube-state-metrics · postgres-exporter — port-forward only, never exposed
forgeforgejo + registry + runner on the cluster, tls by cert-manager, host edge on loopback
lab-04its own docker bridge — only nginx publishes, to the host, loopback
vmsqemu with user-mode nat · one vm per bridge, separate nats, no route between them
exposurenothing faces the internet — every listener is loopback or private

the full map — addresses, ports, and the who-can-reach-whom matrix — lives in the workspace home-lab/network.md.

expansion tracker

7 / 9 complete
donelab-01 · three-tier docker compose2026-11-06

nginx + flask + postgres in one compose file — the baseline stack every later lab re-implements.

donelab-02 · same tiers on a kind cluster2026-11-07

the compose stack translated to kubernetes: deployments, services, configmaps, the secret that is a bag of keys.

donelab-03 · observability layer2026-11-08

metrics-server, kube-state-metrics, prometheus, grafana, postgres-exporter bolted onto lab-02; alerts verified end-to-end with a chaos pod.

donelab-04 · terraform iac2026-11-12

the three tiers declared in hcl — all 8 exercises run: s3 remote state with versioning + locking, the aws provider swap, and the stack instanced twice from a module.

donehome-lab · ansible baseline2026-11-08

network map (addresses, ports, who-can-reach-whom) plus a baseline playbook that is idempotent on both vm — changed=0 on the second run.

doneforge · helm chart on the cluster2026-11-12

forgejo + runner (dind sidecar) + in-cluster registry over tls from cert-manager; the compose forge retired with its volumes kept as a rollback.

donegitops · argo cd deploys the chart2026-11-12

the chart is deployed by argo cd from the forge's own repo — sync-gitops.sh is the only path from editing the chart to a release.

activereverse engineering · workflow

first self-built stripped elf analyzed in the kali vm; five reproducible notes and a reused helper remain for completion.

plannedpublic edge · tunnel + ingress

everything currently faces loopback; going public needs a tunnel (cloudflared) in front of the ingress — deliberately last.

the study

cloud topics in progress — progress is the fraction of the topic worked through, proficiency is the honest self-grade (learning → working → comfortable), evidenced by what actually ran.

docker & composecomfortable

lab-01 compose stack, lab-04 containers via terraform, colima migration after docker desktop, the dind sidecar in the forge runner.

kubernetesworking

labs 02/03 on kind: deployments, services, configmaps/secrets, nodeport vs clusterip, boot-time retries, crashloop forensics.

observabilityworking

prometheus + grafana + ksm + postgres-exporter on the cluster; alert fired → chaos pod deleted → self-resolved, verified end to end.

terraform / iacworking

lab-04: hcl modules, s3 remote state with versioning and locking, provider swap to aws, drift created and destroyed on purpose.

ansibleworking

baseline playbook idempotent on ubuntu + kali (changed=0 second run); learned serial-console debugging when ssh lied.

gitopslearning

argo cd deploys the forge chart from the forge's own repo; sync-gitops.sh is the only release path.

awslearning

scoped iam user limited to the terraform state bucket, root locked behind mfa with no keys, remote state in s3 with versioning and locking, a real bucket created/drifting/destroyed.

networking fundamentalsworking

the home-lab network map: slirp nat quirks, docker bridges 172.17/18/19, the reachability matrix proven by curl, not by belief.

the write-ups of these labs are under blog — the whole arc is from a compose file to a certificate chain.