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

Fix broken links to replicaset examples (#14199)

Browse Source
This commit is contained in:
Karthik Ravikanti
2019-05-07 23:33:51 +08:00
committed by Kubernetes Prow Robot
parent 1054269082
commit 0b0087329b
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/workloads/controllers/replicaset.md
+4 -4
View File
@@ -54,7 +54,7 @@ Saving this manifest into `frontend.yaml` and submitting it to a Kubernetes clus
create the defined ReplicaSet and the Pods that it manages.
```shell
kubectl apply -f http://k8s.io/examples/controllers/frontend.yaml
kubectl apply -f https://kubernetes.io/examples/controllers/frontend.yaml
```
You can then get the current ReplicaSets deployed:
@@ -162,7 +162,7 @@ Suppose you create the Pods after the frontend ReplicaSet has been deployed and
fulfill its replica count requirement:
```shell
kubectl apply -f http://k8s.io/examples/pods/pod-rs.yaml
kubectl apply -f https://kubernetes.io/examples/pods/pod-rs.yaml
```
The new Pods will be acquired by the ReplicaSet, and then immediately terminated as the ReplicaSet would be over
@@ -184,12 +184,12 @@ pod2 0/1 Terminating 0 4s
If you create the Pods first:
```shell
kubectl apply -f http://k8s.io/examples/pods/pod-rs.yaml
kubectl apply -f https://kubernetes.io/examples/pods/pod-rs.yaml
```
And then create the ReplicaSet however:
```shell
kubectl apply -f http://k8s.io/examples/controllers/frontend.yaml
kubectl apply -f https://kubernetes.io/examples/controllers/frontend.yaml
```
You shall see that the ReplicaSet has acquired the Pods and has only created new ones according to its spec until the