Should restart deployment logic also restart other kinds of workloads?

[mcmarkj]

Summary

Currently, the logic to restart a deployment is restricted to just that, deployments. My thought process is that this could be widened so things like statefulsets, daemonsets, replicasets would also be restarted.

Use cases

Secrets are consumed by more than just deployments, so only restarting deployments could cause unexpected results in users environments when only some of of the pods actually restart.

Proposed solution

Widen the scope of the restart logic.

Is there a workaround to accomplish this today?

Not that I'm aware of