[feature request] How to distinguish between in-place restarts and problem pod restarts

[chenshiwei-io]

What would you like to be added:

Version: v1.2 Container Restart FEATURE STATE: Kruise v0.9.0

ContainerRecreateRequest provides a way to let users restart/recreate one or more containers in an existing Pod.

Just like the in-place update provided in Kruise, during container recreation, other containers in the same Pod are still running. Once the recreation is completed, nothing changes in the Pod except that the recreated container's restartCount is increased. Note that the files written into the rootfs of the previous container will be lost, but the data in volume mounts remain.

How to distinguish between in-place restarts and problem pod restartCount ?

Why is this needed: I want to show problem pod restartCount.

[FillZpp]

@no-frown How about a discussion in next community meeting?

[chenshiwei-io]

@no-frown How about a discussion in next community meeting?

👌🏻 Is the discussion in the openkruise dingtalk group? I am in the group.

[hantmac]

How about add an annotation to indicate which container was restarted by crr ?

[FillZpp]

@no-frown How about a discussion in next community meeting?

👌🏻 Is the discussion in the openkruise dingtalk group? I am in the group.

We'd better discuss this on the bi-weekly meeting, which will be notified in the dingtalk group.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.