The problem
Trying the multi-cluster plugin normally means setting up PipeCD and several Kubernetes clusters before anything happens. That is too much for one session, so most people never see a canary rollout across clusters for themselves.
A hands-on workshop for Pre-DevFest Ibadan 2026. Attendees run PipeCD and two Kubernetes clusters on their own laptop, deploy one app to both, and practise previewing, canary rollouts and rolling back.
Trying the multi-cluster plugin normally means setting up PipeCD and several Kubernetes clusters before anything happens. That is too much for one session, so most people never see a canary rollout across clusters for themselves.
I ran this workshop at the Pre-DevFest Ibadan 2026 Cloud Session on 31 October 2026. It turns the Kubernetes multi-cluster plugin I built for PipeCD into something people can try in one sitting, on their own machine.
Each attendee forks the repo and runs one setup script. It starts the PipeCD console and two kind clusters, and a small agent called piped deploys the same app, hello-ibadan, to both clusters whenever they push to their fork.
Every exercise follows the same loop: make a branch, edit the app, preview what will change, then merge to deploy and check both clusters.
The setup downloads about 1.2 GB, so the guide tells attendees to start it straight away and follow along on the projector until it finishes. Anyone without Docker, or with a struggling laptop, can use the no-install path and still work through every exercise. The workshop was tested end to end on macOS with OrbStack, and on Windows it runs inside WSL2.
Built with PipeCD, Kubernetes, kind and shell scripts.