Some of my values: Discipline, Minimalism, Progress, and Lifelong Learning
https://links.andlogreg.work
I've documented how I quickly provision Ubuntu VMs on Proxmox using Terraform and Cloud-Init.
Covers cloning from templates and injecting network/SSH configs automatically. 🔗 ⬇️
andlogreg.work/notes/202512...
andlogreg.work/notes/202512...
Full reference note here: andlogreg.work/notes/202512...
Full reference note here: andlogreg.work/notes/202512...
1. a "UI-optimized" template with QEMU guest agents and VirtIO drivers enabled
2. a "Barebones" version specifically for Terraform to take over. (2/3)
1. a "UI-optimized" template with QEMU guest agents and VirtIO drivers enabled
2. a "Barebones" version specifically for Terraform to take over. (2/3)
Hope this saves someone from the same trap!
#DockerTips #TechNotes #DevLife
Hope this saves someone from the same trap!
#DockerTips #TechNotes #DevLife
- `ARG` before `FROM` → only available to `FROM`
- If you want to use that same `ARG` later, you must re-declare it after `FROM`
✅ Correct:
- `ARG` before `FROM` → only available to `FROM`
- If you want to use that same `ARG` later, you must re-declare it after `FROM`
✅ Correct:
But the condition was never true — even with:
`--build-arg TARGET_ENV=production`.
But the condition was never true — even with:
`--build-arg TARGET_ENV=production`.
Lesson: if a hook is critical, don’t assume it will always run.
Be explicit. Be safe. 🛡️
#Kubernetes #ArgoCD #PlatformEngineering #MLOps #DevOps
Lesson: if a hook is critical, don’t assume it will always run.
Be explicit. Be safe. 🛡️
#Kubernetes #ArgoCD #PlatformEngineering #MLOps #DevOps
That way your app always enforces what it needs. No surprises.
That way your app always enforces what it needs. No surprises.
It’s a normal resource, so it will run even during drift-based auto-syncs — just early in the sync order.
Not perfect, but more predictable.
It’s a normal resource, so it will run even during drift-based auto-syncs — just early in the sync order.
Not perfect, but more predictable.
ArgoCD just re-applies manifests directly — no hook logic involved. 🫣
ArgoCD just re-applies manifests directly — no hook logic involved. 🫣
✅ Manual syncs (via UI or CLI)
✅ Auto-syncs caused by Git changes (e.g. new commits)
What does not?
❌ Auto-syncs triggered by live state drift (e.g. someone running `kubectl edit`)
✅ Manual syncs (via UI or CLI)
✅ Auto-syncs caused by Git changes (e.g. new commits)
What does not?
❌ Auto-syncs triggered by live state drift (e.g. someone running `kubectl edit`)
The thought of losing access is honestly unsettling...
I'll start taking action on making my digital life more resilient soon... 🫡🖖
The thought of losing access is honestly unsettling...
I'll start taking action on making my digital life more resilient soon... 🫡🖖
Maybe I should try alternating—one week digital, one week analog—just to see what works best. Otherwise, I'm just stuck in decision paralysis!
What do you use for journaling? Any tips for choosing between the two or using both together?
Maybe I should try alternating—one week digital, one week analog—just to see what works best. Otherwise, I'm just stuck in decision paralysis!
What do you use for journaling? Any tips for choosing between the two or using both together?