higress-group/higress

Support for merging ServiceEntries of services with the same FQDN name from multiple service registries

Open

#1,641 opened on Jan 3, 2025

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Go (1,219 forks)github user discovery
area/registryhelp wantedlevel/normal

Repository metrics

Stars
 (9,036 stars)
PR merge metrics
 (Avg merge 7d 9h) (18 merged PRs in 30d)

Description

Why do you need it?

Same service registered to different registration centers may conflict and overwrite each other. A reasonable approach is to merge them.

Contributor guide

Research direction
Examine how ServiceEntries are currently created and updated in Higress, especially from multiple registries. Look for existing merging logic or conflicts. Consider proposing a merge strategy, e.g., by FQDN and priority.
Tech stack
go
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Goservice registry concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50