search

nemonik / taiga-helm

A helm chart for Taiga
BSD 3-Clause "New" or "Revised" License
18 stars 20 forks source link

Any reason the chart installs all parts as statefulsets #12

Open ibotty opened 2 years ago

ibotty commented 2 years ago

Is there any reason to run the components as statefulsets? taiga-front, taiga-gateway and taiga-protected can be deployed as regular Deployments I assume that the lifecycle guarantees of a statefulset are also not neccessary for taiga-back and taiga-events. Am I overlooking something?

maxirus commented 2 years ago

So StatefulSet is used to scale stateful workloads, or ones that require a PVC. Using the official docker-compose as source of truth, it appears taiga-front, taiga-events, and taiga-protected do NOT have volumes and thus should beDeployments, not StatefulSets.

ibotty commented 2 years ago

Deployments can also require a PVC. The difference is that a StatefulSet can get different PVC per replica. That's certainly not needed with taiga. Statefulsets have different characteristics of restart, etc., but I doubt that necessary here. I wonder which parts of taiga can be run concurrently, if state is only in the DB and on the file system. If so it should be possible to run many replicas of each component for HA.