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

Update replicaset.md (#7961)

Browse Source 
Fixed the 404 error in : https://github.com/kubernetes/website/issues/7924
This commit is contained in:
Rajakavitha1
2018-04-04 21:05:10 +05:30
committed by zacharysarah
parent 5a85aed682
commit b74b5779ab
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/concepts/workloads/controllers/replicaset.md
+5 -5
View File
@@ -23,12 +23,12 @@ whereas a Replication Controller only supports equality-based selector requireme
Most [`kubectl`](/docs/user-guide/kubectl/) commands that support Most [`kubectl`](/docs/user-guide/kubectl/) commands that support
Replication Controllers also support ReplicaSets. One exception is the Replication Controllers also support ReplicaSets. One exception is the
[`rolling-update`](/docs/user-guide/kubectl/{{page.version}}/#rolling-update) command. If [`rolling-update`](/docs/reference/generated/kubectl/kubectl-commands/{{page.version}}/#rolling-update) command. If
you want the rolling update functionality please consider using Deployments you want the rolling update functionality please consider using Deployments
instead. Also, the instead. Also, the
[`rolling-update`](/docs/user-guide/kubectl/{{page.version}}/#rolling-update) command is [`rolling-update`](/docs/reference/generated/kubectl/kubectl-commands/{{page.version}}/#rolling-update) command is
imperative whereas Deployments are declarative, so we recommend using Deployments imperative whereas Deployments are declarative, so we recommend using Deployments
through the [`rollout`](/docs/user-guide/kubectl/{{page.version}}/#rollout) command. through the [`rollout`](/docs/reference/generated/kubectl/kubectl-commands/{{page.version}}/#rollout) command.
While ReplicaSets can be used independently, today it's mainly used by While ReplicaSets can be used independently, today it's mainly used by
[Deployments](/docs/concepts/workloads/controllers/deployment/) as a mechanism to orchestrate pod [Deployments](/docs/concepts/workloads/controllers/deployment/) as a mechanism to orchestrate pod
@@ -154,7 +154,7 @@ If you do not specify `.spec.replicas`, then it defaults to 1.
### Deleting a ReplicaSet and its Pods ### Deleting a ReplicaSet and its Pods
To delete a ReplicaSet and all its pods, use [`kubectl To delete a ReplicaSet and all its pods, use [`kubectl
delete`](/docs/user-guide/kubectl/{{page.version}}/#delete). Kubectl will scale the ReplicaSet to zero and wait delete`](/docs/reference/generated/kubectl/kubectl-commands/{{page.version}}/#delete). Kubectl will scale the ReplicaSet to zero and wait
for it to delete each pod before deleting the ReplicaSet itself. If this kubectl command is interrupted, it can for it to delete each pod before deleting the ReplicaSet itself. If this kubectl command is interrupted, it can
be restarted. be restarted.
@@ -163,7 +163,7 @@ When using the REST API or go client library, you need to do the steps explicitl
### Deleting just a ReplicaSet ### Deleting just a ReplicaSet
You can delete a ReplicaSet without affecting any of its pods, using [`kubectl delete`](/docs/user-guide/kubectl/{{page.version}}/#delete) with the `--cascade=false` option. You can delete a ReplicaSet without affecting any of its pods, using [`kubectl delete`](/docs/reference/generated/kubectl/kubectl-commands/{{page.version}}/#delete) with the `--cascade=false` option.
When using the REST API or go client library, simply delete the ReplicaSet object. When using the REST API or go client library, simply delete the ReplicaSet object.