fediversity/fediversity

nodes can find one another #785

New issue

Closed

opened 2026-03-17 20:17:58 +01:00 by kiara · 1 comment

kiara commented

2026-03-17 20:17:58 +01:00

Owner

As a hosting provider,
I want for discoverability to ensure relevant nodes can find one another,
so that ephemeral nodes may be replaced with limited down-time.

implementation notes

traditionally, it seems hashicorp consul targeted this type of use-case. given they have switched license to BSL though, a potential alternative seems doing etcd + CoreDNS.
alternatively, distributed schedulers (#598) should likely already cover this concern.
c.f. the complementary concern of #633 (nodes identifying one another)

**As** a hosting provider, **I want** for discoverability to ensure relevant nodes can find one another, **so that** ephemeral nodes may be replaced with limited down-time. ### implementation notes - traditionally, it seems [hashicorp consul](https://www.hashicorp.com/en/products/consul) targeted this type of use-case. given they have switched license to BSL though, a potential alternative seems doing [etcd](https://etcd.io/) + [CoreDNS](https://coredns.io/). - alternatively, distributed schedulers (#598) should likely already cover this concern. - c.f. the complementary concern of #633 (nodes identifying one another)

kiara added the

type: user story

label

2026-03-17 20:17:58 +01:00

kiara added a new dependency

2026-03-17 20:18:30 +01:00

#228 [D2.3] brought into production [2027-11-01]

kiara referenced this issue

2026-03-17 20:19:07 +01:00

[D2.3] brought into production [2027-11-01] #228

kiara added a new dependency

2026-06-07 18:19:05 +02:00

#954 demo env broken

kiara added the

label

2026-06-12 00:43:58 +02:00

kiara referenced this issue from a pull request that will close it,

2026-06-29 13:12:47 +02:00

internal DNS: nodes find each other via BIND populated by octodns (#785) #1146

kiara referenced this issue from a commit

2026-06-29 18:32:46 +02:00

internal DNS: nodes find each other via BIND populated by octodns (#785) (#1146)

kiara commented

2026-06-29 18:34:41 +02:00

Author

Owner

the consul use-case seems aimed at auto-scaling, so that'll have to remain a follow-up. for now let's call this closed in #1146 then.

the consul use-case seems aimed at auto-scaling, so that'll have to remain a follow-up. for now let's call this closed in #1146 then.

kiara removed a dependency

2026-06-29 18:34:48 +02:00

#954 demo env broken

kiara closed this issue

2026-06-29 18:34:56 +02:00

Sign in to join this conversation.

No labels

application-offering

configure-applications

ambition/install-applications

update-applications

user-management

component: fediversity panel

component: nixops4

estimation high: >3d

estimation low: <2h

estimation mid: <8h

infinite points

project-management

role: application developer

role: application operator

role: hosting provider

role: maintainer

type: deliverable

type: key result

type: objective

type: user story

user experience

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks

#228 [D2.3] brought into production [2027-11-01]

fediversity/fediversity

Reference

fediversity/fediversity#785

No description provided.