When I joined SUSE I heard about our Kubernetes distributions: Rancher Kubernetes Engine (RKE), RKE2 and K3s. However, the differences between RKE and RKE2 were not clear to me. I decided to spend time with them and blog about the differences.
Releasing software to users has become a sophisticated and intricate process that requires high levels of consistency and coordination. A release has to be built, brought together, documented, tested and deployed, which requires coordination of at least four separate teams and a generous handful of pipelines and other tools. Without a well-documented process things can get messy very quickly, causing stress for everyone involved.
Whether you’re part of a team managing SaaS products or a high-security digital workspace, sometimes Things Go Wrong and must be addressed with extreme care, professionalism, and predictability. For outages, data breaches, vulnerabilities and more, you and your team are juggling a variety of tools, processes, and rigid incident management systems. When the on-call pager goes off at 3 am almost no one has the ability to remember every step needed to kick off all the response workflows.
The Apps Framework is an important tool in the Mattermost developer toolbox for easily creating integrations and customized workflows—written in any language and deployed with serverless hosting. The Apps Framework complements the existing ecosystem of plugins, slash commands, bots, and webhooks. As of Mattermost version 6.6, the Apps Framework is now generally available for all cloud and self-hosted deployments.
The DevOps field is engaged in a great, collective migration into the cloud. Businesses are decentralizing their applications and databases, hosting them in the cloud to make them available regardless of geography or user device. Some organizations choose to host their applications on private servers, but in periods of high demand take advantage of the public cloud by directing overflow traffic to cloud servers. This approach is called cloud bursting.
Monitoring your on-premise or hybrid infrastructure means keeping track of potentially thousands of devices, any one of which could be a point of failure. Additionally, silos between application and network teams can create visibility gaps that complicate troubleshooting. For network engineers investigating bottlenecks, being able to view real-time infrastructure health and performance data alongside application metrics is essential for ensuring their organizations meet key SLOs.
