News for hackers. Stuff that matters.
Re:Kubernetes by Example by dominotw on Wednesday May 31, 2017 @11:29AM (#14453255)
A replication controller (RC) is a supervisor for long-running pods.

A deployment is a supervisor for pods and replica sets

So what's the difference between these supervisors?

Re:Kubernetes by Example by teraflop on Wednesday May 31, 2017 @11:40AM (#14453351)
They basically serve the same purpose, but Deployments move more of the "state" into the Kubernetes API controller.

For example, the standard way to do a rolling update using RCs is to create a new RC that is responsible for the updated pods, and then gradually increase/decrease the replica counts to reach the desired state. This is conceptually simple, but the downside is that the Kubernetes API doesn't know anything about the relationship between the old and new controllers. All the responsibility is pushed to the client.

With Deployments, both the old and new configurations are first-class objects. So you can view the history of previous configurations, and you can query the progress of a rolling update. You also get better-defined behavior when multiple clients are trying to concurrently make changes, because Kubernetes can arbitrate between them at a higher level.

Re:Kubernetes by Example by Zikes on Wednesday May 31, 2017 @11:32AM (#14453285)
From https://kubernetes.io/docs/concepts/workloads/controllers/re...

> A ReplicaSet ensures that a specified number of pod “replicas” are running at any given time. However, a Deployment is a higher-level concept that manages ReplicaSets and provides declarative updates to pods along with a lot of other useful features. Therefore, we recommend using Deployments instead of directly using ReplicaSets, unless you require custom update orchestration or don’t require updates at all.

Re:Kubernetes by Example by jbeda on Wednesday May 31, 2017 @12:37PM (#14453848)
A Pod manages a set of containers on a node.

A ReplicaSet (RCs are old and deprecated) manages a set of Pods. It has a template and a target replica count.

A Deployment manages ReplicaSets across versions/upgrades. When you change a deployment it creates a new ReplicaSet and does a rolling upgrade from new to old version by tweaking replica counts in new and old ReplicaSets.

Re:Kubernetes by Example by drdaeman on Wednesday May 31, 2017 @11:32AM (#14453284)
Deployments are newer concept. The evolution was: Replication Controllers -> Replica Sets -> Deployments.

I don't think the differences are well-documented, though.