From f3ffbdb7f40046697244e94a29ccef9e50620076 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pau=20Ru=C5=80lan?= Date: Tue, 12 Apr 2016 10:03:57 +0200 Subject: [PATCH] Replica set clarification: no need to manipulate directly --- docs/user-guide/replicasets.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/user-guide/replicasets.md b/docs/user-guide/replicasets.md index ae755b69fa..b2b9b02ee3 100644 --- a/docs/user-guide/replicasets.md +++ b/docs/user-guide/replicasets.md @@ -36,7 +36,10 @@ provides declarative updates to pods along with a lot of other useful features. Therefore, we recommend using Deployments instead of directly using Replica Sets, unless you require custom update orchestration or don't require updates at all. -### Example +This actually means that you may never need to manipulate Replica Set objects: +use directly a Deployment and define your application in the spec section. + +## Example {% include code.html language="yaml" file="replicasets/frontend.yaml" ghlink="/docs/user-guide/replicasets/frontend.yaml" %} @@ -44,7 +47,7 @@ Saving this config into `frontend.yaml` and submitting it to a Kubernetes cluste create the defined replica set and the pods that it manages. ```shell -$ kubectl create -f frontend.yaml +$ kubectl create -f frontend.yaml replicaset "frontend" created $ kubectl describe rs/frontend Name: frontend