Welcome to Essential Coach
Production-proven VMware Aria Automation, NSX, and Ansible solutions from real customer engagements.
Essential Coach shares battle-tested customer success stories — the technical challenges, the implementations, the lessons learned, and the open-source code that came out of them. Whether you’re modernizing a legacy vRO environment, integrating BlueCat IPAM with Aria Automation, untangling NSX Federation network profiles, or building idempotent Ansible post-deploy pipelines, you’ll find practical, production-ready guidance here.
What You’ll Find Here
- Customer success stories — Real implementations, not marketing case studies. The challenges faced, the patterns discovered, the lessons learned.
- Open-source automation — Production-grade code on GitHub, sanitized of customer-identifying detail and ready for adaptation.
- Practical guidance — Battle-tested patterns for VMware Aria Automation, NSX Federation, BlueCat IPAM, vRealize Orchestrator, and Ansible.
- Hard-won lessons — What worked, what didn’t, what we’d do differently. The patterns that survive contact with production.
Why “Essential”?
Not every feature, just what matters. Not every automation, just what works. Essential Coach focuses on production-proven solutions that solve real problems at real scale — the patterns that earn their place in the runbook.
Ready to Explore?
Browse the Customer Success Stories for individual workstream deep-dives. Visit Automation Downloads to grab the open-source repositories. Or reach out at noah@essential.coach to talk about a similar engagement at your organization.
Latest Stories
The Certificates Expired a Year After a Date Nobody Was Watching: Five TKG Clusters Back From the Supervisor
Five VKS guest clusters on VCF 9.1.1, every API server down, every control plane certificate expired on the anniversary of a node rollout nobody remembered. Where TKG certificates actually live, why kubeadm’s renewal can hand you a certificate no client accepts, why the nodes have to be done in series when there is no quorum, and the script that took three production clusters from connection refused to READY in an afternoon.
Everything That Cost Us a Day Returned Success: Nine Versions of esx_ready.sh on a Live Fleet
One day, three fires, nine versions of esx_ready.sh on a live VCF 9.1.1 fleet, and nothing crashed: an upgrade that reported success and moved nothing, a cluster leave that released no disks, a depot staged onto the vSAN cache disk, a retried SDDC Manager task reading stale inventory. The build gate VCF 9.1.1 enforces, the chain of vSAN disk ownership, the feature that had to be deleted, and the stub harness that turned every failure into a test before its fix shipped.
Importing ESXi 8 Into VCF 9.1 When ESX 9 Won’t Run on the Hardware
ESX 9 won’t run on Broadwell and VCF 9.1.1 won’t commission ESXi 8, so the clusters are built on vSphere 8 and imported. The vCenter upgrade that removed an NSX collision, the fourteen steps a cluster has to pass before VCF will take it, and the rules the tooling lives by. Behind a fresh 9.1.1 vCenter, two more: a distributed switch an ESXi 8 host cannot join, and a cluster born without the vLCM image the import needs.