Skip to content

Commit aefee41

Browse files
committed
editing as per the reviews received
Signed-off-by: Ritikaa96 <[email protected]>
1 parent ac2933c commit aefee41

File tree

1 file changed

+10
-4
lines changed
  • content/en/docs/reference/labels-annotations-taints

1 file changed

+10
-4
lines changed

content/en/docs/reference/labels-annotations-taints/_index.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1281,12 +1281,18 @@ Type: Annotation
12811281
12821282
Example: kubectl.kubernetes.io/restartedAt: "2024-06-21T17:27:41Z"
12831283
1284-
Used on: Pod
1284+
Used on: Deployment, ReplicaSet, StatefulSet, DaemonSet, Pod
12851285
1286-
This annotation contains the latest restart time of a resource(Deployment, ReplicaSet, StatefulSet or DaemonSet).
1286+
This annotation contains the latest restart time of a resource (Deployment, ReplicaSet, StatefulSet or DaemonSet),
1287+
where kubectl triggered a rollout in order to force creation of new Pods.
12871288
The command `kubectl rollout restart <RESOURCE>` triggers a restart by patching the template
1288-
metadata of all the pods of resource with this annotation. You can also trigger a restart by manually
1289-
setting or changing the value of this annotation. In above example the latest restart time of resource is shown as 21st Jun 2024 17:27:41 GMT.
1289+
metadata of all the pods of resource with this annotation. In above example the latest restart time is shown as 21st June 2024 at 17:27:41 UTC.
1290+
1291+
You should not assume that this annotation represents the date / time of the most recent update;
1292+
a separate change could have been made since the last manually triggered rollout.
1293+
1294+
If you manually set this annotation on a Pod, nothing happens. The restarting side effect comes from
1295+
how workload management and Pod templating works.
12901296

12911297
### endpoints.kubernetes.io/over-capacity
12921298

0 commit comments

Comments
 (0)