Break point: Lens, Kong Mesh, Spring Boot, Git Tower, and Amazon AppStream

break point

Kubernetes IDE Lens 5.3 has just made it over the finish line, and fits the project with new filtering capabilities, terminal copy on select, a cluster sidebar dropdown, and an URL display to web link URLs. The update also might be worth a look, as Lens learned to support port forwarding with HTTPS and includes a feature/port forward dashboard.

Kong Mesh gets role-based access control

Not just Istio received an upgrade this week — service meshes Kuma and its commercial equivalent Kong Mesh also got the chance to up their version number. Kuma now comes with a user token authentication mechanism, gateway support for external services, and the option of informing CA managers about all relevant backends during the enable step. Kong Mesh users will also be happy to learn that their mesh finally offers role-based access control and knows how to work with Windows virtual machines. 

Spring Boot 2.6 is here

Spring app development framework Spring Boot was recently released in version 2.6, providing users with ways to test Spring MVC via WebTestClient, automatic configuration for spring-rabbit-stream, and support for pluggable rules for sanitizing properties in /env and configprops. Developers can now also set SameSite attributes on session cookies for servlet applications, and configure health groups on selected ports.

Git Tower for Windows changes for the darker

Windows users of Git Tower had to wait a while for a major upgrade to their Git client but version 3.0 is finally ready — and with it, the completely reworked UI.

After having installed the latest iteration, developers are treated to refreshed interface, a dark mode, improved search features, and quick actions to facilitate performing operations via keyboard only. The Git Tower team also worked to improve the performance of their tool’s Windows flavour, simplify navigation, and added a way of grouping commits by date.

Amazon AppStream introduces serverless fleet type

With the recent launch of Amazon AppStream 2.0, AWS’s application streaming service gained a serverless fleet type for streaming applications from a managed pool of instances, so that developers don’t have to handle capacity management and the like themselves anymore. These so-called Elastic fleets were created with use-cases with sporadic usage patterns in mind and are said to work with applications that can be run from virtual hard disks without configurations. Example scenarios listed on the AWS website include software trials, trainings, and sales demos.