In the previous release of Botkube we promised to accelerate the pace of development and release. Well, here is another new release of Botkube, the most modern ChatOps tool for Kubernetes!

BotKube v0.14.0 addresses a number of community-suggested issues and adds some great features to help you control the notification levels you receive from your Kubernetes clusters.

If you have any feature requests or bug reports, reach out to us on Slack or submit a Github issue

In this release, we focused on improvements to the Botkube onboarding experience and notification tuning, persistent settings, and bug fixes. Some of the enhancements are currently Slack-specific using the additional interactive capabilities of the new Slack app. We plan to enhance other platforms with interactive features where technically feasible.

Dynamic notification setting changes

We've received frequent feedback from users about the notification settings in Botkube. By default, Botkube monitors and shows all Kubernetes events in a configured communication channel. Previously, this could only be configured in the YAML configuration or during the Helm installation/upgrade.

You can now also configure notification settings right from the Botkube interface in your communication platform. Using the command @Botkube edit SourceBindings you can select the notifications you want to receive. After choosing the notifications, the configuration is dynamically updated with an automatic brief restart of Botkube.

New Botkube Slack App

We have created a brand new Botkube Slack app. The new app uses the Slack Socket Mode which provides a much more robust platform for interactivity and uses the new Slack permissions model for enhanced security.

You will see many enhancements to Botkube in Slack in this and upcoming releases. For example, you can use the interactive selector to change the notification settings mentioned earlier. Just run @Botkube, edit SourceBindings without specifying the notification level, and you can select the sources from an interactive dialog.

The installation process has changed for the new Slack app. See the installation guide to get started with the enhanced interactive experience.

The legacy Slack app is still available, but will be deprecated in future versions.

Improved Help

The @Botkube help command has been enhanced when using the new Botkube Slack app. Run @Botkube help and you will see an interactive help message. You can click any of the buttons in the interactive help to run the commands, change settings, and more.

This new, interactive help will enable new Botkube users to get up and running even faster. You can also send us feedback and access documentation and additional external help resources directly from the interactive help.

Persistent Settings

Changes to settings made from the Botkube interface, such as notifier start/stop, notification level settings, and filter enable/disable now persist across Botkube restarts. In earlier versions, these settings would reset to the settings in the Botkube configuration file upon restarting the Botkube pod.

Mattermost v7 Support

Botkube now supports Mattermost version 7.x! See the installation guide for Mattermost to get started.

Bug Fixes

We have fixed several bugs in BotKube that were reported to us by users. We also spent some time refactoring code and increasing test coverage to improve the quality of BotKube. You can see the list of bug fixes in the changelog.

We appreciate your bug reports and pull requests! If you notice a bug in BotKube, please report it as a GitHub issue and we are happy to collaborate with you on getting it resolved.

Feedback - We'd Love to Hear From You!

As always, we want to hear your feedback and ideas about BotKube. Help us plan the BotKube roadmap, get the features you'd like implemented, and get bugs fixed quickly.

You can talk to us in the BotKube GitHub issues, BotKube Slack community, or email our Product Leader at blair@kubeshop.io.