ROS 2 From a historical lab to a verified one
Today the lab has a Jazzy image whose talker and listener work inside one container, and a historical three-VM cluster. This plan is how it earns the claim that ROS 2 messages cross between Kubernetes nodes. Each of the four phases has its own page.
Where the lab stands today
Three honest states, so the plan has a starting line. Nothing below is claimed beyond what the repository's checks show.
ROS 2 Jazzy image
A Jazzy / Ubuntu 24.04 image builds in CI, and a talker and listener exchange messages inside one container. This does not show messages crossing Kubernetes pods or workers.
Three-VM Vagrant cluster
The original lab uses ROS 2 Foxy (end of life), Kubernetes 1.29 and Weave Net. It stays as a historical example and needs about 30 GB of VM memory.
Messages across workers
No check yet proves a ROS 2 message travels between different Kubernetes nodes on a modern profile. The whole plan exists to earn that proof.
Step through the 90 days
Press play, or pick a phase. The marker shows the order of the work. It is not a progress report.
Four phases, one gate
Illustration · sequence onlyThe gate sits at the end of phase 2: a clean host runs the supported install, shows messages between different workers and passes the documented verification. Until then the modern quickstart stays unpublished.
Pick a phase
Every phase page has its own animation, the exact issues, and what "done" means.
Define the reference path
Pick the supported profile and design the cross-worker discovery test.
Open phase 1 Days 15–30Make it runnable and safe
One command, a lighter cluster, and safer defaults.
Open phase 2 Days 31–60Package and document
README, benchmarks, tutorials and a first validated release.
Open phase 3 Days 61–90Grow with evidence
Demo, posts, real user reports and honest measurement.
Open phase 4 Definition of doneRelease gates
The eight checks a supported release must pass. None is claimed yet.
Open the gates ResearchResearch scenarios
Four open experiments that build on a verified lab.
Explore scenariosHow to read this plan
Targets, not promises
- A phase can slip. The plan holds a milestone rather than skip a release gate.
- A successful Docker build or a lint pass is not a substitute for end-to-end ROS 2 verification.
- No usage, star or performance numbers are published here until they are measured and sourced.
Help move a phase forward
Every phase is a set of public issues. Pick a small one, comment that you would like to work on it, and open a pull request.