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.
Different components use different db, as follows:
controlleruse db 0passportuse db 1grafanause db 2builderuse db 3manageruse db 10helmbrokeruse db 11
The above are the default configurations for each component.
A Container image for running standalone (not clustered) Valkey on a Kubernetes cluster.
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.