4 ms·
I would recommend updating this to describe ReplicaSets[1] over ReplicationControllers. They are very similar and serve the same purpose, but the huge differenc
by cyphar 9y ago
I would recommend updating this to describe ReplicaSets[1] over ReplicationControllers. They are very similar and serve the same purpose, but the huge difference is that ReplicaSets have selector support -- meaning that you can require N replicas of pods that have X selector (rather than requiring N replicas of pods with the exact same spec).
[1]: https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/ https://kubernetes.io/docs/concepts/workloads/controllers/re...
- pcthrowaway 9y agoI tend to agree, as ReplicaSets are, as the k8s docs describe, the 'next-generation replication controller', though I couldn't find a place where they state that RCs are in fact deprecated. The section on service discovery constructs an example using RCs, and I'm guessing other sections do as well, so the change may be non-trivial.
- smarterclayton 9y agoRS is still beta though, so while they're the future, RCs aren't going anywhere for a long time. In general use RS (or even better, deployments) and don't worry about it.