mailgun / mailgun/groupcache

how to use group cache with k8s container deployment

Open
#70 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
539
Forks
76
PR merge metrics
No merged PRs in 30d

Description

How to use group cache with k8s container deployment. Application would autoly scale in k8s.
so, how to resolve this problem.
Currently it seems some feature must be added in groupcache.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named. Start by clarifying how groupcache should behave when Kubernetes automatically scales containers, including membership and cache ownership; done requires an agreed implementation or documented approach for that deployment model.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
cloud, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.