• Jonathan Whitaker

    Jonathan Whitaker

    7 months ago
    I've started working on a statefulset based Helm chart for spicedb. You can find it here:https://github.com/jonwhitty/helm-charts/tree/master/charts/spicedb The goal is to make it more fully featured. Right now it just supports an absolutely minimum viable Helm chart to install a multi-node spicedb cluster. It's been used by our team already to manage a multi-node spicedb cluster with dispatching. More work is coming to wire up the TLS settings and everything, but hopefully it helps some of ya'll out there in the community already 👍 Feel free to contribute as well 😃.
  • e

    ecordell

    7 months ago
    what specifically is broken? that issue is about some unwanted log lines, I don't think it should affect any behavior
  • Jonathan Whitaker

    Jonathan Whitaker

    7 months ago
    🤦‍♂️ For some reason I took those logs as error outputs and mistakenly thought the request failed. I'm sorry about that. False alarm 🤣
  • e

    ecordell

    7 months ago
    whew! no worries
  • t

    trichner

    7 months ago
    @User we're also considering running a cluster, if I may ask, what's the reason for the statefulness? As far as I can see a simple deployment would also do, right?
  • Jonathan Whitaker

    Jonathan Whitaker

    7 months ago
    Yeah, a deployment should work fine as well because underneath the cover kuberesolver is used to establish the cluster membership. I'm just used to these types of "clustered" deployments being a statefulset, and so that's the only reason. If there are any dependencies on node1 coming online before node2, node3, etc.. then it'll be nice as a statefulset. But yeah, it could be a deployment. What do you think? Should I just change it to a deployment?
  • t

    trichner

    7 months ago
    Yes, changing it to a deployment would probably be a good idea 🙂 Not sure if there are any spicedb internals that would profit from statefulness though. (i.e. cache on disk?)
  • Jonathan Whitaker

    Jonathan Whitaker

    7 months ago
    What's your reasoning though? I don't really see much value over a deployment vs a statefulset for a spicedb rollout. In fact, a statefulset gives us more options in the event that a gradual rollout or cache on disk etc.. become a dependency.
  • t

    trichner

    7 months ago
    (I'm not from authzed, just another engineer interested in the same) My thoughts:- it's easier to argue about the state in general since everything is ephemeral - it's straight forward to understand and deploy, there will be no questions around if/what of the state might need a backup - a stateful-set with only 1 replica can not do zero-downtime deployments (arguably not that important if you anyways run a cluster)
  • Joey

    Joey

    7 months ago
    for the record, we run using a deployment as well