Skip to content

docs: add Kubernetes Helm installation notes #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mberlofa wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: add Kubernetes Helm installation notes #16

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e7f9c90
docs: add kubernetes helm installation notes
mberlofa Jul 2, 2026
43ab0fa
docs: address kubernetes pool review
mberlofa Jul 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 38 additions & 0 deletions content/serverguide/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,6 +69,44 @@ make && make test && sudo make install

See `./configure --help` for full options.

### On Kubernetes with Helm

One Kubernetes option is the HelmForge chart. For a standard memcached pool,
start several independent servers and configure the application client to spread
keys across all of them.

For example, this starts three memcached servers:

```yaml
architecture: distributed
replicaCount: 3
```

Install it with Helm:

```
helm repo add helmforge https://repo.helmforge.dev
helm repo update
helm install memcached helmforge/memcached -f values.yaml
```

Memcached does not replicate entries between servers. In this setup each pod is

@dormando dormando Jul 2, 2026 •
edited
Loading

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This whole paragraph can be removed; it's redundant with the rest of the documentation site, and all clients support pools since that is our default mode of operation. A note could be left around consistent hashing being preferred, but you need to say why ie; kube is likely to shoot nodes randomly and consistent hashing causes less disruption. that is information that is relevant to this specific text (something kube does that is unnatural) and links it back into known info (consistent hashing disrupts less when pools change)

The sentence below about "With the release name above" is good.

@mberlofa mberlofa Jul 2, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. I removed the redundant paragraph, kept the headless Service example, and added a shorter Kubernetes-specific note explaining why consistent hashing helps when pods or nodes are replaced.

an independent memcached server, and the application client is responsible for
choosing a server for each key. Use a client library that supports multiple
servers, ideally with consistent hashing.

With the release name above, clients that need explicit pool members can use the
headless Service names:

```
memcached-0.memcached-headless:11211
memcached-1.memcached-headless:11211
memcached-2.memcached-headless:11211
```

See the [HelmForge memcached chart](https://github.com/helmforgedev/charts/tree/main/charts/memcached)
for chart values and production notes.

### Install a client

Memcached on its own is just a key/value storage daemon. Installing it does
Expand Down