submariner-io/lighthouse

DNS service discovery across connected Kubernetes clusters.

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

submariner-io/lighthouse has 150+ stars and 40+ forks on GitHub, is written in Go, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 21 minutes ago
Added to GitGenius on October 15th, 2026
Created on July 15th, 2019
Open Issues & Pull Requests: 8 (+0)
GitHub issues: Enabled
Number of forks: 42
Total Stargazers: 150 (+0)
Total Subscribers: 9 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.7 hours
Mean response time: 36.5 days
90th percentile: 94.2 days
Tracked items: 26

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 472 days
Stale 30+ days: 5
Stale 90+ days: 5

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (10)
  • bug (8)
  • priority:medium (8)
  • stale (6)
  • mcs-api-alignment (5)
  • priority:low (5)
  • help wanted (3)
  • technical-debt (3)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Lighthouse is a DNS service discovery tool for Kubernetes clusters connected by Submariner in multi-cluster environments.

Lighthouse solves the problem of enabling DNS-based service discovery across multiple Kubernetes clusters that are networked together through Submariner. It works by providing DNS resolution capabilities that allow services in one cluster to discover and communicate with services in other connected clusters. The solution is designed to be compatible with any CNI plugin, making it flexible for different network configurations.

Lighthouse is suited for organizations running multi-cluster Kubernetes deployments where workloads need to discover and access services across cluster boundaries using standard DNS mechanisms. It is particularly valuable when you have already adopted Submariner for cross-cluster networking and need a corresponding service discovery layer. The tool integrates with Submariner's architecture rather than operating as a standalone solution, so it is most appropriate for teams already committed to the Submariner ecosystem.

The project maintains active development workflows including periodic testing, release image generation, and flake detection to catch intermittent test failures. The codebase follows established best practices for infrastructure projects and welcomes external contributions through a documented development guide.