From ab16e815d5214f9929ab17e63f588269fabc9c28 Mon Sep 17 00:00:00 2001 From: Steven Rombauts Date: Wed, 19 Mar 2025 15:11:42 +0100 Subject: [PATCH] Self-Hosted: Explain how to fix unhealthy Kurl pods when upgrading --- docs/self-hosted/kubernetes-troubleshooting.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/self-hosted/kubernetes-troubleshooting.md b/docs/self-hosted/kubernetes-troubleshooting.md index 2d8828c6..fb758683 100644 --- a/docs/self-hosted/kubernetes-troubleshooting.md +++ b/docs/self-hosted/kubernetes-troubleshooting.md @@ -8,6 +8,15 @@ If the dashboard shows: Please refer to the "[Updates](./kubernetes-maintenance.md#updates)" section in our maintenance guide. +#### Installer fails during update + +If the kURL installer exits with the error message `Kurl has unhealthy Pod(s)` before starting the actual upgrade, it usually means +there are older pods stuck in an invalid state from previous runs. You can remove these with this command and try again: + +``` +kubectl delete pods --field-selector status.phase=Failed -n kurl +``` + #### Generating a support bundle You can generate a support bundle from the Replicated Management Console on port