mirror of
https://github.com/siderolabs/discovery-service.git
synced 2025-03-14 09:55:08 +00:00
49e53b1473
This addresses a pretty race case when cluster GC runs while the cluster just got created without any affiliates, but with a subscription. Client first watches cluster state, then adds an affiliate, so there might be a case when GC runs and sees a fresh cluster without any affiliates and GCes it. This also fixes test instability. Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
Talos Discovery Service (for KubeSpan)
Discovery Service provides cluster membership and KubeSpan peer information for Talos clusters.
Overview
Discovery Service provides centralized service for Talos nodes to exchange information about nodes of the cluster.
Talos runs "official" instance of the service, and anyone can run their own instance on-prem or in the cloud.
Discovery service doesn't store any data, all data is ephemeral and is kept only in memory. Node information is expired (if not updated) after 30 minutes. Discovery service doesn't see actual node information, it only stores and updates encrypted blobs. Discovery data should be submitted encrypted by the client, and service doesn't have the encryption key.