@@ -231,7 +231,7 @@ have some limitations:
231
231
- If the ` metadata.deletionTimestamp ` is set, no new entry can be added to the
232
232
` metadata.finalizers ` list.
233
233
- Pod updates may not change fields other than ` spec.containers[*].image ` ,
234
- ` spec.initContainers[*].image ` , ` spec.activeDeadlineSeconds ` , ` spec.terminationGracePeriodSeconds ` or
234
+ ` spec.initContainers[*].image ` , ` spec.activeDeadlineSeconds ` , ` spec.terminationGracePeriodSeconds ` ,
235
235
` spec.tolerations ` or ` spec.schedulingGates ` . For ` spec.tolerations ` , you can only add new entries.
236
236
- When updating the ` spec.activeDeadlineSeconds ` field, two types of updates
237
237
are allowed:
@@ -268,6 +268,10 @@ The above update rules apply to regular pod updates, but other pod fields can be
268
268
to track the pod state to the current pod status. The pod's ` status.observedGeneration ` will reflect the
269
269
` metadata.generation ` of the pod at the point that the pod status is being reported.
270
270
271
+ {{< note >}}
272
+ The ` status.observedGeneration ` field is managed by the kubelet and external controllers should ** not** modify this field.
273
+ {{< /note >}}
274
+
271
275
Different status fields may either be associated with the ` metadata.generation ` of the current sync loop, or with the
272
276
` metadata.generation ` of the previous sync loop. The key distinction is whether a change in the ` spec ` is reflected
273
277
directly in the ` status ` or is an indirect result of a running process.
@@ -296,7 +300,7 @@ This behavior applies to:
296
300
request.
297
301
- ** Container state** : During an in-progress resize, with require restart policy reflects the previous generation's
298
302
request.
299
- - ** activeDeadlineSeconds** & ** terminationGracePeriodSeconds** & ** DeletionTimestamp ** : The effects of these fields on the
303
+ - ** activeDeadlineSeconds** & ** terminationGracePeriodSeconds** & ** deletionTimestamp ** : The effects of these fields on the
300
304
Pod's status are a result of the previously observed specification.
301
305
302
306
## Resource sharing and communication
0 commit comments