PublishDiscoveryFleet
norsk-mgr’s fleet discovery server: the Manager stores it and sends each connected node, and each node at its hello, the access minted for it. Protocol 1.4.
Request Type: PublishDiscoveryFleetRequest
norsk-mgr’s fleet discovery server, published so the Manager can hand each node its access (worker.proto DiscoveryFleetAccess). The Manager keeps the latest and sends it on every stream. Protocol 1.4.
Field |
Type |
Repeated |
Description |
address |
host:port nodes reach the fleet discovery server at. Empty: each node keeps the address it derives from its manager URL. |
||
token |
The leaf token; empty for a fleet that asks its clients for none. |
||
tier_secret |
The tier secret node tokens are minted from. Stored by the Manager and never sent to a node. |
||
addresses |
✅ |
Every replica of the discovery replica set, host:port each (protocol
1.7). Empty: |
Response Type: PublishDiscoveryFleetResponse
Field |
Type |
Repeated |
Description |
forwarded_to |
How many worker streams it was sent on. |
||
tier_secret |
The tier secret and leaf token IN FORCE (protocol 1.7). The first ones published stay: a later publish carrying different ones keeps these, so a second member’s norsk-mgr, or a rebuilt host, cannot change every node’s token. The publisher adopts what comes back. |
||
token |
|||
secrets_kept |
True when this publish carried a different secret or token and the ones already in force were kept. |
||
tier_secret_alt |
The second tier secret every replica also accepts while a rotation is under way (RotateDiscoveryTierSecret); empty otherwise. |