How would you measure the success of Mirantis's Kubernetes Engine (MKE)?

Introduction

Measuring the success of Mirantis's Kubernetes Engine (MKE) requires a comprehensive approach that considers various stakeholders and metrics. To effectively evaluate MKE's performance, I'll follow a structured framework covering core metrics, supporting indicators, and risk factors while considering all key stakeholders.

Step 1

Product Context

Mirantis Kubernetes Engine (MKE) is an enterprise-grade container orchestration platform that simplifies the deployment, management, and scaling of containerized applications. It's designed for organizations looking to modernize their infrastructure and adopt cloud-native technologies.

Key stakeholders include:

1. Enterprise IT teams: Seeking efficient container management
2. Developers: Requiring a stable, feature-rich platform
3. Operations teams: Needing robust monitoring and security features
4. Business leaders: Looking for cost-effective, scalable solutions

User flow typically involves:

1. Cluster deployment: IT teams set up MKE clusters
2. Application deployment: Developers push containerized apps to MKE
3. Monitoring and management: Ops teams oversee cluster health and performance
4. Scaling and optimization: IT and ops collaborate to adjust resources as needed

MKE fits into Mirantis's broader strategy of providing end-to-end cloud and container solutions for enterprises. It competes with platforms like Red Hat OpenShift and VMware Tanzu, differentiating itself through its integration with other Mirantis products and focus on ease of use.

In terms of product lifecycle, MKE is in the growth stage, with a established user base but still evolving features and expanding market share.