Incident classification is a standardized way of organizing incidents with established categories. Incidents can include outages caused by errors in code, hardware failures, resource deficits — anything that disrupts normal operations. Each new incident should fit into a category dependent on the areas of the service affected, and in a ranking of the severity of the incident. Each of these classifications should have an established response procedure associated with it.

Rancher and SAP have been working on a dedicated verification of SAP Data Intelligence 3 (SAP DI) on Rancher Kubernetes Engine (RKE) cluster and Longhorn storage platform. This blog will guide you on how to properly install SAP DI on an RKE cluster.

I’m excited to announce that Rancher has signed a definitive agreement to be acquired by SUSE. Rancher is the most widely used enterprise Kubernetes platform. SUSE is the largest independent open source software company and a leader in enterprise Linux. By combining Rancher and SUSE, we not only gain massive engineering resources to further strengthen our market-leading product, we are also able to preserve our unique 100% open source business model.

Talking about competition can be hard. It’s understandable. Product positioning can be touchy subjects especially when those use cases overlap. In the DevOps space, event-driven architectures are certainly not a new concept. Companies like Netflix, LinkedIn, and Facebook have in-house tools built specifically for this type of automation. However, Relay’s mission is make it easy for everyone to build event-driven workflows – not the Netflix-es of the world.

Monitoring requires a multi-faceted approach if DevOps teams want end-to-end visibility and deep insight into issues. This is especially true in the case of modern microservices applications, which are essentially collections of distributed services that talk to each other over a service mesh. With monolithic applications, requests can be tracked easily from the client to the server and back, but with modern applications, every request passes through numerous services before completion.

ROS, Ripple and reflections – In this month’s edition of The State of Robotics, we’ll tell you about the recently discovered Ripple vulnerability, the latest and greatest in robots reflecting nature, and a dash of news from the ROS universe.

In our series of blog posts based on Automated Containerization, here is another quick read on why Enterprises should invest in containerization of applications instead of Lift-and-Shift approach. Legacy applications can be slow and expensive to maintain. If you use the Lift-and-Shift approach to migrate applications to cloud is relatively inexpensive, but ongoing operating costs can be exactly the opposite. The contention is that applications perform and evolve relative to their environments.

Lifecycle management is one of the most complicated components of Kubernetes. In a past article, we showed how to modify a cluster to change the type and size of its nodes. In this post, we will explain how to upgrade the Kubernetes version of a Tanzu Kubernetes cluster when there is a new release. And the best part is that it’s all done in just a few easy steps using the Tanzu Kubernetes Grid Service for vSphere.

CEO Ashar Rizqi had the pleasure of being a guest on Google Cloud OnAir, a Google Cloud Customer Interview Series. Ashar and interviewer Jimmy Sopko discussed how Blameless has extended our runway using Google Cloud and Google Kubernetes Engine and how the team cultivates a culture of site reliability in a changing world.

Secrets, by definition, should be kept secret, whichever tool you’re using. While there are plenty of best practices for keeping your Kubernetes secrets actually secret, there are some loopholes that can compromise their security, and might be taken advantage of by malicious entities. This post will cover prevalent best practices for securing your secrets on Kubernetes along with some new approaches for secrets management.