whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #364 from APSL/replicaset-tip

Browse Source 
Replica set clarification: no need to write directly
This commit is contained in:
johndmulhausen
2016-05-24 16:25:35 -07:00
parent 5a10b7fb99 f3ffbdb7f4
commit 8d8d80c3ce
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/user-guide/replicasets.md
+5 -2
View File
@@ -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 Therefore, we recommend using Deployments instead of directly using Replica Sets, unless
you require custom update orchestration or don't require updates at all. 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" %} {% 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. create the defined replica set and the pods that it manages.
```shell ```shell
$ kubectl create -f frontend.yaml $ kubectl create -f frontend.yaml
replicaset "frontend" created replicaset "frontend" created
$ kubectl describe rs/frontend $ kubectl describe rs/frontend
Name: frontend Name: frontend