By Bhawani Singh10 min read
Connecting a Mac build host to a private EKS cluster
A private EKS cluster drives macOS builds on a local Mac without inbound access, using an outbound SSM tunnel and disposable VMs.
Series · 7 posts
Running macOS Builds from Tekton
Run macOS builds from Tekton on disposable VMs. Follow the integration from private-cluster access to failure recovery and faster startup, including who owns cleanup after Tekton stops waiting.
1
2
By Bhawani Singh10 min read
Running macOS builds from Tekton with a CustomRun
A Tekton CustomRun delegates builds to a macOS VM, with the controller tracking build results and waiting for confirmed VM deletion on normal completion.
3
By Bhawani Singh8 min read
Passing source and artifacts between Tekton and a macOS VM
Source and artifacts move between Tekton and a macOS VM through an OCI registry, with digest checks that caught an empty archive copied from a successful compilation.
4
By Bhawani Singh8 min read
Tracking a macOS build until its VM is deleted
A host journal tracks macOS build outcomes separately from VM deletion, with seven pipeline runs covering success, failure, cancellation and environment rejection before cloning.
5
By Bhawani Singh11 min read
Recovering macOS builds when the controller or agent stops.
A macOS build can run twice after an agent restart, and Tekton can time out before its VM is deleted. Recovery needs durable results, one retry owner and independent cleanup.
6
By Bhawani Singh14 min read
Starting macOS builds in seconds instead of half a minute
A fresh, pre-booted macOS VM cuts startup from 26s to 4.7s, including a similar saving through Tekton, at the cost of one VM slot and about 10 GiB of combined VM process RSS.
7
By Bhawani Singh11 min read
Should you run macOS jobs from Tekton?
A CustomRun connects Tekton to disposable macOS VMs, but choosing that integration means owning results, retries and cleanup after Tekton stops waiting, with runner integrations offering another…