What's New in Version 0.3.89

This section contains information about the new features and changes in the Management Console introduced in version 0.3.89.

  2 minute read  

Step into the improved Management Console version 0.3.89! This release unfolds a new chapter in our development journey with several notable backend changes. Not only have these adjustments enabled a slew of captivating features, like adding a kubeconfig directly from the management console and detailed progress bars, but they also herald the initiation of GUI support for deploying Benthos containers. As we roll out these advancements, rest assured, we’ve also resolved numerous bugs to enhance the overall usability of the Management Console.

Initial GUI Support for Benthos Containers

Embarking on an exciting path, our team has enabled GUI support for deploying Benthos containers. While it currently supports OPC/UA as a data source, plans to extend its capability are well underway.

A Stronger Backend

Our team dedicated significant resources to improve the backend, setting a strong foundation for this update’s new features. Anticipate a smoother, more seamless interaction with the Management Console moving forward.

Direct Kubeconfig Addition

Eliminating the need for Lens, users can now add a kubeconfig directly from the management console to link existing devices to their account. With options to save the kubeconfig on the local filesystem or in the kubeconfigs directory, convenience is a click away.

Enhanced Progress Indicators

Our pursuit to better the user experience continues with the introduction of progress bars and detailed logs, offering more insight into the events during Management Console start-up, USB flashing, and installation processes.

Resolved Glitches

  • A glitch causing switched accounts to display devices from the previous account on the overview page has been addressed.
  • The USB flashing page now ensures the Management Console initiation was as an admin.
  • Seamless communication between the front and backend is now facilitated by automatic port selection when the default is unavailable.
  • The frontend now patiently waits for the first pod to be ready before indicating that setup is finished.