k8s-based discovery mechanism #406
Description
Description
Would there be any appetite for upstreaming a kubernetes-based Discoverer implementation?
Given that it would introduce a dependency on a k8s client library, is there a precedent for reducing the bloat for users who don't need it, e.g. a jvm-libp2p-contrib library?
Motivation
Many peer workloads run in cloud environments where:
- UDP multicast is either disabled or requires inconvenient infrastructure changes to work
- Trusted peer discovery mechanisms already exist, which we'd like to leverage (e.g. coredns, k8s watch api, e.t.c)
Current Implementation
mDNS is awesome for local development and/or networks which don't block multicast, but not practical on WANs or restricted private cloud networks
Are you planning to do it yourself in a pull request ?
Yes