Worker autoregistration #25

New issue

Open

opened 2025-12-23 16:13:14 +00:00 by just1602 · 0 comments

just1602 commented

2025-12-23 16:13:14 +00:00

I was wondering if the coordinator API was only exposed on the local VM / machine or if it was exposed publicly to the workers?

The idea would be to be able, for a worker who has network access to the coordinator to register itself automatically based on the coordinator URL instead of having to register a new worker manually.

The workflow I'd love to see is the following:

create VPS / microvm / containers using opentofu or nix
deploy botanix worker on the newly created VPS / microvm / containers
forget about it, workers just setup themselves automatically without any intervention

Another avenue could be to use vault / openbao:

setup vault / openbao to have access to the coordinator API
deploy new workers on VPS / microvm / containers
let the workers contact vault to get a token from the coordinator and give it to them

Apparently I can't edit labels, but that would clearly be low priority.

I was wondering if the coordinator API was only exposed on the local VM / machine or if it was exposed publicly to the workers? The idea would be to be able, for a worker who has network access to the coordinator to register itself automatically based on the coordinator URL instead of having to register a new worker manually. The workflow I'd love to see is the following: 1. create VPS / microvm / containers using opentofu or nix 2. deploy botanix worker on the newly created VPS / microvm / containers 3. forget about it, workers just setup themselves automatically without any intervention Another avenue could be to use vault / openbao: 1. setup vault / openbao to have access to the coordinator API 2. deploy new workers on VPS / microvm / containers 3. let the workers contact vault to get a token from the coordinator and give it to them --- Apparently I can't edit labels, but that would clearly be low priority.