hcavarsan/kftray v0.20.1

KFtray - v0.20.1

on GitHub

[0.20.1] - 2025-07-12

Context

In previous versions, using kftray had some problems. Bad configuration files could cause the app to crash without a clear reason. Port-forwarding could run forever, using up computer resources, because there was no way to set a timeout. Users had to add the Kubernetes context to their configuration files, which was an extra step. Also, if the network connection was lost, port-forwards would break and users had to restart them by hand.

Addressing the Issues

This release fixes these problems with new features and improvements.

New Features

• Settings Management and Port Forward Timeout. You can now manage app settings from the UI. A new feature lets you set a timeout for port-forwards, so they close automatically after a set time. This helps save computer resources. Your settings are saved and will be there the next time you open the app. This was added in PR #444.

• Configuration Validation. The app now checks your configuration files when you import them. If something is wrong, you will get a clear message instead of the app crashing. This was added in PR #443.

• Optional Context Field. You no longer have to enter a context in your configuration files. If you leave it blank, the app will use your current kubeconfig context, just like kubectl does. This was added in PR #446.

Improvements

• Network Monitor Refactoring and Settings. The network monitor code is now shared between the GUI and TUI apps. This means it will work the same way on both. You can also turn the network monitor on or off in the new settings menu. This was improved in PR #447.

• Improved Logs Navigation. Navigating logs in the TUI with PageUp and PageDown now works correctly. The logs are also easier to read. This was improved in PR #443.

Bug Fixes

• Improved Port Forward Reconnection. Port-forwarding is now more stable. The app will automatically try to reconnect if you lose your network connection, like when your computer wakes from sleep. This means you won't have to restart them manually as often. This was fixed in PR #445.