We're back with our weekly updates (v0.22) after a big bug squash session.
The major theme for this week is performance and reliability. The data within Infra.app should update in real-time, and we saw from some of your reports / live troubleshooting sessions that there was a problem with stale data. This should now be fixed along with many of the requested bug fixes (changelog below).
Thank you to everyone who's sent in bug reports, feature requests and information on your setup. It's super helpful to us as we build out Infra. Some of the features suggested by you are already in the works -- many will take some time as we go through a couple of iterations on the design.
We're super excited about what's to come! If you prefer to manually download the update, it's available at https://infra.app/download
- Some users have experienced stale data. We've changed how Infra.app performs data refreshes, especially when the computer sleeps/resumes from sleep
- If the connection to a Kubernetes cluster is lost, Infra.app will try to automatically reconnect without spamming the cluster
- Fetching Workloads now will use less data - and speed is improved
- Fixed issue where metrics would temporarily show 0.00 for all workloads when switching clusters
- Fixed issue where configmaps would not appear in Workload Overview page
- Fixed sidebar namespaces flickering when changing clusters
- "Show System Workloads" will be on by default if there are no other workloads
- Infra.app will now only fetch the logs since last seen up to 50k lines (older logs are cached)
- Fixed an issue where logs will stop streaming when pods are added / removed from Workload
- Fixed an issue where logs stream will delay when pods are restarted
- Fixed issue where connectivity errors not linked to the workload would show up as lines in workload logs