From d04d15f50640f66a44b6945159013be2ded84625 Mon Sep 17 00:00:00 2001 From: Scott Brenner Date: Mon, 4 Feb 2019 15:25:03 -0800 Subject: [PATCH] replicationController -> ReplicaSet (#12487) Proposing replacing `replicationController` with `ReplicaSet` here since ["ReplicaSet is the next-generation Replication Controller."](https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/). --- .../en/docs/tasks/job/fine-parallel-processing-work-queue.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/job/fine-parallel-processing-work-queue.md b/content/en/docs/tasks/job/fine-parallel-processing-work-queue.md index d96f5ed986..3f0de4e884 100644 --- a/content/en/docs/tasks/job/fine-parallel-processing-work-queue.md +++ b/content/en/docs/tasks/job/fine-parallel-processing-work-queue.md @@ -249,7 +249,7 @@ If running a queue service or modifying your containers to use a work queue is i want to consider one of the other [job patterns](/docs/concepts/jobs/run-to-completion-finite-workloads/#job-patterns). If you have a continuous stream of background processing work to run, then -consider running your background workers with a `replicationController` instead, +consider running your background workers with a `ReplicaSet` instead, and consider running a background processing library such as [https://github.com/resque/resque](https://github.com/resque/resque).