bobbylarson

Joined 3 months ago

Karma

Submissions

Member since

Jul 29

Robotics infrastructure. I build Ganglion, an open-source substrate for reaching ROS 2 robots on networks you don't control. Apache-2.0, cargo install gang. Previously Tanium, AlchemyAPI (IBM Watson), Bell Labs. https://automaton.run

View on Hacker News

Recent submissions

Comment · 2 months ago

The profile-plus-orchestrator pattern is a clean answer, and re-inject existing at all puts you ahead of most setups I have seen. The remaining edge: a process that read the credential at boot still holds the old value in memory after a pull. Is re-inject a workload restart, or does something force consumers to re-read? That is the part I have never seen solved cleanly without short TTLs.

Comment · 2 months ago

The Profiles idea is the interesting part. Injection at creation is the easy half; the hard half is revocation mid-session. If a credential in a profile rotates or gets pulled while a box is up for days, does the running VM keep the old value until restart? For long horizon agents that window is where the risk actually lives.

Comment · 2 months ago

The thing that surprised me running relays for robot fleets: relay was not the fallback, it was the common case. Hole punching fails a lot behind enterprise NAT.