Home / BeaverDeck / Docs / Insights Guide / Workload Insights / Pod Restarts

Pod Restarts

BeaverDeck uses this check to identify a specific workload condition that may need operator review.

Permissions: viewing checks requires insights: view. Opening a linked object or logs requires the corresponding resource permission, and the BeaverDeck ServiceAccount must be allowed to read the Kubernetes resources used by the check. Suppressing a finding requires insights: edit and affects all users.

Check type	`pod-restarts`
Insights section	Workload Insights
Alert severity	Warning

When It Reports A Finding

The total restart count across init and application containers is at least 3.

Why This Is A Problem

Repeated restarts indicate instability and can reduce availability, hide intermittent failures, and increase load on dependencies.

Recommended Response

Identify the containers contributing to the total and inspect previous logs and termination reasons.
Review probes, dependencies, configuration, resource pressure, and application startup behavior.
Correct the owning workload and monitor whether restart counts continue to increase.

Scope And Limitations

The threshold is cumulative and has no time window. A long-running pod with old, resolved restarts can still appear until it is replaced.

After remediation: refresh Workload Insights and verify the underlying resource or metric. Suppress the finding only when the condition is intentional and its risk is accepted.