Skip to main content

Kviklet 0.3 Release Notes

· 3 min read
Jascha Beste

Kviklet 0.3 is out! We've added a bunch of new features and improvements to make your production access even more secure and efficient. The new release contains a bunch of new features most notably:

  • An integration with Kubernetes Exec, you can now run commands on other pods after they've been approved through kviklet. The idea behind this is that you can audit your script executions through Kviklet as well as database acces. If this works well we will expand on this further with e.g. a web based console some time?
  • Support for MS SQL Server Databases. A wish by the community, if you have other databases that you'd like us to support don't hesitate to open an issue!
  • The connection settings have gotten an overhaul so you can now edit all details of a connection after you've created it (except the id)
  • Requests with multiple results will now be shown in a paginated matter. So you can put all your selects in a single Request (Or mix in updates and deletes if you really want to).
  • After running a statement the audit entry will now contain a little bit of metadata for what happened (rows affected/returned), so not everything is gone if you close the tab.
  • Configurable max executions per connection, allows configuring connections so that the same request can be executed more than once (1 is still the default though).
  • Fixed all timestamp bugs (no more -2 hours ago on comments, we hope...)

This release marks the first release where we don't only focus on database production access but also provide a feature that allows running bash commands on your kubernetes cluster. This feature is a bit of a change in direction for kviklet as DB access has been the main focus point fo Kviklet so far. But conceptually it does make sense that you would want to audit all your production access and not just the database access. We are excited to see how this feature is received and if it will be used by users. We also believe the is a lot of potential to expand into this direction and cover more use cases and different technology in the future if this works well.

The next release will focus on improving the experience around adding roles and permissions. Currently if you do not want to use our default setup of roles you run into a bit of an ugly UI and probably have no idea what to do there. For 0.4 we plan to change that and make this experience easier and way more intuitive. The permission system itself might also need a bit of an overhaul.

If you have any feedback or feature requests, please don't hesitate to reach out to us via a github issue or on our webpage. We are always happy to hear from users and improve the product based on feedback.