Skip to content

Self-Hosted: Explain how to fix unhealthy kURL pods when upgrading #126

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 19, 2025
Merged

Self-Hosted: Explain how to fix unhealthy kURL pods when upgrading #126

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/self-hosted/kubernetes-troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down