8000 GitHub - drycc/valkey · GitHub
[go: up one dir, main page]

Skip to content
dryccPublic

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

1 watching

Forks

Latest commit

 

History

118 Commits

Folders and files

Repository files navigation

Drycc Valkey

Build Status

Drycc (pronounced DAY-iss) Workflow is an open source Platform as a Service (PaaS) that adds a developer-friendly layer to any Kubernetes cluster, making it easy to deploy and manage applications on your own servers.

Usage

Different components use different db, as follows:

  • controller use db 0
  • passport use db 1
  • grafana use db 2
  • builder use db 3
  • manager use db 10
  • helmbroker use db 11

The above are the default configurations for each component.

Description

A Container image for running standalone (not clustered) Valkey on a Kubernetes cluster.

Proxy and high availability

Each Valkey pod includes an HAProxy 3.4.0 sidecar. Clients that do not support Sentinel can connect to drycc-valkey:16379 instead of discovering the current primary themselves.

HAProxy routes traffic only to a node that reports role:master and is also named as the primary by a majority of Sentinels. The winning node must be the only node with a majority. Sentinel remains responsible for monitoring and failover. If no unique primary qualifies, including when a majority of Sentinels is unreachable, HAProxy rejects new connections rather than risking writes to a stale primary. When a backend is marked down, its existing sessions are closed so clients can reconnect to the new primary.

Port 8404 exposes HAProxy's own /healthz endpoint for Kubernetes probes. It is internal to the pod and is not published through the Valkey Service.

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

1 watching

Forks

Releases

Packages

Contributors

Languages

0