Skip to content

Commit 5f48ae0

Browse files
Update replicaset.md
1 parent 0ce9c35 commit 5f48ae0

File tree

1 file changed

+14
-15
lines changed

1 file changed

+14
-15
lines changed

content/en/docs/concepts/workloads/controllers/replicaset.md

Lines changed: 14 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -90,17 +90,16 @@ And you will see output similar to:
9090
Name: frontend
9191
Namespace: default
9292
Selector: tier=frontend
93-
Labels: app=guestbook
93+
Labels: app=nginx
9494
tier=frontend
95-
Annotations: kubectl.kubernetes.io/last-applied-configuration:
96-
{"apiVersion":"apps/v1","kind":"ReplicaSet","metadata":{"annotations":{},"labels":{"app":"guestbook","tier":"frontend"},"name":"frontend",...
95+
Annotations: <none>
9796
Replicas: 3 current / 3 desired
9897
Pods Status: 3 Running / 0 Waiting / 0 Succeeded / 0 Failed
9998
Pod Template:
10099
Labels: tier=frontend
101100
Containers:
102-
php-redis:
103-
Image: gcr.io/google_samples/gb-frontend:v3
101+
nginx:
102+
Image: nginx
104103
Port: <none>
105104
Host Port: <none>
106105
Environment: <none>
@@ -109,9 +108,9 @@ Pod Template:
109108
Events:
110109
Type Reason Age From Message
111110
---- ------ ---- ---- -------
112-
Normal SuccessfulCreate 117s replicaset-controller Created pod: frontend-wtsmm
113-
Normal SuccessfulCreate 116s replicaset-controller Created pod: frontend-b2zdv
114-
Normal SuccessfulCreate 116s replicaset-controller Created pod: frontend-vcmts
111+
Normal SuccessfulCreate 13s replicaset-controller Created pod: frontend-gbgfx
112+
Normal SuccessfulCreate 13s replicaset-controller Created pod: frontend-rwz57
113+
Normal SuccessfulCreate 13s replicaset-controller Created pod: frontend-wkl7w
115114
```
116115

117116
And lastly you can check for the Pods brought up:
@@ -124,16 +123,16 @@ You should see Pod information similar to:
124123

125124
```
126125
NAME READY STATUS RESTARTS AGE
127-
frontend-b2zdv 1/1 Running 0 6m36s
128-
frontend-vcmts 1/1 Running 0 6m36s
129-
frontend-wtsmm 1/1 Running 0 6m36s
126+
frontend-gbgfx 1/1 Running 0 10m
127+
frontend-rwz57 1/1 Running 0 10m
128+
frontend-wkl7w 1/1 Running 0 10m
130129
```
131130

132131
You can also verify that the owner reference of these pods is set to the frontend ReplicaSet.
133132
To do this, get the yaml of one of the Pods running:
134133

135134
```shell
136-
kubectl get pods frontend-b2zdv -o yaml
135+
kubectl get pods frontend-gbgfx -o yaml
137136
```
138137

139138
The output will look similar to this, with the frontend ReplicaSet's info set in the metadata's ownerReferences field:
@@ -142,19 +141,19 @@ The output will look similar to this, with the frontend ReplicaSet's info set in
142141
apiVersion: v1
143142
kind: Pod
144143
metadata:
145-
creationTimestamp: "2020-02-12T07:06:16Z"
144+
creationTimestamp: "2024-02-28T22:30:44Z"
146145
generateName: frontend-
147146
labels:
148147
tier: frontend
149-
name: frontend-b2zdv
148+
name: frontend-gbgfx
150149
namespace: default
151150
ownerReferences:
152151
- apiVersion: apps/v1
153152
blockOwnerDeletion: true
154153
controller: true
155154
kind: ReplicaSet
156155
name: frontend
157-
uid: f391f6db-bb9b-4c09-ae74-6a1f77f3d5cf
156+
uid: e129deca-f864-481b-bb16-b27abfd92292
158157
...
159158
```
160159

0 commit comments

Comments
 (0)