Skip to content

Conversation

@losh11
Copy link
Member

@losh11 losh11 commented Jun 14, 2022

No description provided.

lispmeister and others added 6 commits January 11, 2022 17:44
LSEED uses port 53 (DNS) to provide joining LND nodes with a list of
existing nodes on the Lightning network. Unfortunately services on port
53 are a bit difficult to provide behind the regular Kubernetes LB or
ingress controller. In particular the fact that LSEED answers queries
on both the UDP and TCP protocol makes it difficult to run in a
Kubernetes environment.

To solve the issues describe above this commit provides the following
code changes:

- enhanced logging for events that add new nodes to the LSEED node list
- a Dockerfile to create a containerized version of LSEED
- new parameters with separate listener addresses for UDP and TCP
- a separate listener for UDP and TCP requests utilizing these new
  parameters
- a couple of typo fixes to the Debugf statements in lseed and
  tests
Problem: We need to enable LSEED to run as a Kubernetes pod/service
Allow connection to lnd backends for signet and testnet4.
lseed: add support for testnet4 and signet
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants