News for hackers. Stuff that matters.
Re:Teaching Kubernetes by gtirloni on Sunday February 19, 2017 @11:17AM (#13680354)
In K8s that's called "Stateful Sets" (beta in v1.5).

https://kubernetes.io/docs/concepts/abstractions/controllers...

Re:Teaching Kubernetes by lobster_johnson on Sunday February 19, 2017 @02:25PM (#13681414)
You can solve this without StatefulSets, it's just a manual process, and requries that you (1) don't use a replication controller (edit: rather, you use a controller with "replicas: 1"), and (2) can ensure that a single pod claims the data volume.

StatefulSets are more geared towards apps that manage their own redundancy, such as Cassandra or Aerospike, where adding another instance is a matter of just starting it. One of the things that a StatefulSet permits is to preserve the network identity of a pod. For example, if you wanted deploy Cassandra without StatefulSets, you'd deploy each instance as a separate Deployment + Service pair, called, let's say, cassandra-1, cassandra-2 and so on. You would not be able to use Kubernetes' toolsets to scale the cluster. Each instance would use a persistent volume, so effectively it would be almost exactly like a StatefulSet, except Kubernetes would not be handling the pod replication.

In the case of something like Postgres, you'd probably not get any benefit from using a StatefulSet for the master (since only one instance can run), but you can use a StatefulSet to run read-only replicas.

Re:Teaching Kubernetes by gtirloni on Sunday February 19, 2017 @03:17PM (#13681742)
Without Stateful Sets, or a replication controller, doesn't it mean that if my host dies, the DB won't get started anywhere? Who's managing where that pod should spawn next (with its associated storage)?
Re:Teaching Kubernetes by lobster_johnson on Sunday February 19, 2017 @03:29PM (#13681804)
Right, I simplified a bit there: You would use a replication controller, but it would have "replicas: 1". This way, the pod is rescheduled and the service repointed, and the volume management ensures that the database gets mounted.
Re:Teaching Kubernetes by gtirloni on Sunday February 19, 2017 @05:44PM (#13682592)
Got it, thanks!
Re:Teaching Kubernetes by smarterclayton on Sunday February 19, 2017 @06:55PM (#13683027)
Note that replicas: 1 does not actually guarantee "at most 1". If you have block storage with locks (AWS/gce/ceph/cinder), then he second replica won't start until the first is gone. If you try to use "replicas: 1" with a shared filesystem you can have 2 pods running against that filesystem at once.

StatefulSets guarantees "at most one"

Re:Teaching Kubernetes by lobster_johnson on Sunday February 19, 2017 @07:20PM (#13683170)
That's solved by setting "strategy.type" to "Recreate", isn't it? This will disable rolling deploys. The replication controller wouldn't then attempt to have two pods running at the same time.