Intermittent error hints

[ngc4579]

Hi,

I'm currently evaluating sofka as an alternative to k9s as my 'daily driver' when it comes to operational tasks within our k8s clusters.

First of all - everything looks and feels awesome and quite 'snappy'. Thanks for your effort, much appreciated.

Now, from time to time there's an error hint at the bottom of the screen showing:

error: watch stream failed: Error reading events stream: ServiceError: error reading a body from connection

What exactly does that mean, is it of any relevance, and if so - how can I mitigate that?

Best wishes
Karsten

PS - Besides, as a small (rather cosmetic) suggestion: a warm burnout colour scheme would be even more awesome... 😎

[nklmilojevic]

Hi Karsten, thanks for the feedbac!

This message means Sofka lost the connection used to receive Kubernetes resource updates. Sofka automatically retries, but the displayed data can be out of date until the connection recovers.

If it happens occasionally and updates resume, you usually do not need to take action. A network interruption, proxy timeout, or API server connection closure could cause this. The message alone does not tell us which one.

Could you share your Sofka and Kubernetes versions, how often this happens, and whether updates continue afterward? If it keeps happening, start Sofka with SOFKA_LOG=debug sofka. The :info view shows the log location.

The error message should also make it clear that Sofka is retrying.

Thanks for the Warm Burnout suggestion too, I'll keep it in my mind!

[nklmilojevic]

#743

this should also fix most of those wherever they happen

[ngc4579]

@nklmilojevic Great, thanks a lot for your answer and the immediate additional fix. - We're on Kubernetes 1.35, Sofka was 0.29.5 (now 0.29.6). Updates actually did seem to continue afterwards. I'll have an eye on this in the next few days. 🙃