Peer pods autodiscovery within kubernetes cluster
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 539
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I am experimenting with a simple standalone package to automatically keep pod peers up-to-date within a kubernetes cluster:
https://github.com/udhos/kubegroup
Recipe currently looks like this:
groupcachePort := ":5000"
// 1. get my groupcache URL
myURL, errURL = kubegroup.FindMyURL(groupcachePort)
// 2. spawn groupcache peering server
pool := groupcache.NewHTTPPool(myURL)
server := &http.Server{Addr: groupcachePort, Handler: pool}
go func() {
log.Printf("groupcache server: listening on %s", groupcachePort)
err := server.ListenAndServe()
log.Printf("groupcache server: exited: %v", err)
}()
// 3. spawn peering autodiscovery
go kubegroup.UpdatePeers(pool, groupcachePort)
// 4. create groupcache groups, etc: groupOne := groupcache.NewGroup()
Does it look reasonable!?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked kubegroup package and the issue's usage flow through kubegroup.FindMyURL, groupcache.NewHTTPPool, and kubegroup.UpdatePeers. Determine whether Kubernetes peer autodiscovery belongs in groupcache and what behavior or integration would be required; the issue currently asks only whether the approach is reasonable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- distributed-systems, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100