Operations | Monitoring | ITSM | DevOps | Cloud

A little over 2 months ago, we announced Mattermost Omnibus (beta). Mattermost Omnibus is a new, time-saving approach to installing Mattermost. Since then, we’ve done a massive amount of testing, listened to your feedback, and added new features and options. Today, I’m excited to share some big news. The project is officially graduating from Beta status and is ready for any single-server deployments for use as test, dev and/or production Mattermost servers.

Over the course of 2020, Community events have changed. We’ve seen sweeping changes in everything from the way people get together online, to the way they interact, to the platforms they use to meet. Mattermost is a Community-driven company, and as such we continue to try to work and interact with our Community as much as we possibly can.

We’re excited to announce the release of GitHub Plugin version 2.0, which adds some new features that increase productivity and reduce the need to context switch between Mattermost and GitHub. As usual, our open source community members have played a key role in developing all of these features and I’d like to say “Thank You!” for their help. Our GitHub plugin is one of the most popular integrations on Mattermost and we use it every day as part of our development process.

One of the key benefits of using Kubernetes is that it’s very flexible and fault tolerant. However, that also means that it has quite a lot of complexity to deal with. A well-built operator abstracts that complexity away and helps manage updates and upgrades seamlessly. The Mattermost Kubernetes operator is basically like having a Mattermost Cloud Engineer running inside your Kubernetes cluster managing Mattermost for you.