New

Reliability

Misconfiguring Kubernetes workloads can lead to application downtime. Fortunately, Kubernetes offers recommendations for different configurations and best practices, to ensure applications remain fault-tolerant, and to keep users up and running.

👁️ Overview

As part of our proactive Reliability Management offering, Komodor can now surface some of those misconfigurations to help you align with best practices, and to improve your reliability posture over time. Additionally, the detected violations are prioritized based on the runtime impact they had.

We also expanded the best practice checks to include an additional violation - SPoF (Single Point of Failure). In case we detect relevant misconfigurations along with a runtime issue (node issue/termination that led to an availability issue), a SPoF violation will be created.

🗣️ Motivation

Utilizing Komodor's troves of context to tie between best practice violations, misconfigurations, and how they affect your application's performance. With the correct configuration, single points of failure can be avoided, making your application much more reliable.

🚀 Getting Started

The feature is now GA and automatically activated for all accounts!

• Simply navigate to the Reliability Management screen and you will be able to browse between all the best practice violations that Komodor detected, assess their impact, and remediate.
• To configure the policy's thresholds navigate to the Reliability Policies tab and edit it directly through Komodor