From 34a31f41ba232a9ac280d8fbad18a1ad19fb4dce Mon Sep 17 00:00:00 2001 From: Ahmet Alp Balkan Date: Thu, 17 Nov 2016 15:07:13 -0800 Subject: [PATCH] List Deployment next to ReplicationController RestartPolicy section gives an example of what kind of controller should be used for what type of workload. However it only lists rc for web-server type workloads. Adding Deployment next to rc as well. Signed-off-by: Ahmet Alp Balkan --- docs/user-guide/pod-states.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user-guide/pod-states.md b/docs/user-guide/pod-states.md index b29270e5f8e19..8f745e9f56e1a 100644 --- a/docs/user-guide/pod-states.md +++ b/docs/user-guide/pod-states.md @@ -66,8 +66,8 @@ The possible values for RestartPolicy are `Always`, `OnFailure`, or `Never`. If Three types of controllers are currently available: - Use a [`Job`](/docs/user-guide/jobs/) for pods which are expected to terminate (e.g. batch computations). -- Use a [`ReplicationController`](/docs/user-guide/replication-controller/) for pods which are not expected to - terminate (e.g. web servers). +- Use a [`ReplicationController`](/docs/user-guide/replication-controller/) or [`Deployment`](/docs/user-guide/deployments/) + for pods which are not expected to terminate (e.g. web servers). - Use a [`DaemonSet`](/docs/admin/daemons/): Use for pods which need to run 1 per machine because they provide a machine-specific system service. If you are unsure whether to use ReplicationController or Daemon, then see [Daemon Set versus