higress-group/higress

Support Etcd as Service Registry

Open

#385 opened on Jun 17, 2023

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (1,219 forks)github user discovery
area/registryhelp wantedlevel/challengesig/controller

Repository metrics

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

Description

Why do you need it?

etcd is a distributed key value store that provides a reliable way to store data across a cluster of machines. etcd gracefully handles leader elections during network partitions and will tolerate machine failure, including the leader.

How could it be?

A clear and concise description of what you want to happen. You can explain more about input of the feature, and output of it.

Other related information

Add any other context or screenshots about the feature request here.

Contributor guide

Research direction
Understand the existing service registry abstraction in Higress (e.g., Nacos or consul support). Then implement a new etcd registry by wrapping the etcd Go client (etcd/clientv3). Focus on registration, discovery, and health checking.
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
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60