Miropsupgrade readiness
Install

Kubernetes upgrade readiness tool

Upgrade Kubernetes with confidence.

Mirops mirrors your cluster, checks compatibility, and shows exactly what to fix before an upgrade.

Self-host freeSee how it works

Open source under Apache-2.0 · on-prem, EKS, AKS, GKE

Mirror operations

One report. Two interfaces.

See the full picture in Headlamp, or make the same deterministic decision part of every delivery pipeline.

Mirror your cluster

The operator inventories workloads, services, nodes, PVCs, add-ons and their dependencies into a logical mirror.

Analyze readiness

Rules evaluate health, capacity, stability and Compatibility. Optional AI can add reasoning, but never makes the gate decision.

See the blast radius

Risk propagates across the dependency graph and is aggregated per namespace, so teams can see what breaks and where.

Get a verdict

The report is SAFE, WARNING or CRITICAL, with every deterministic blocker listed explicitly.

Gate it in CI

Run the same report through mirops scan --enforce. The CLI exits non-zero when decision.allow is false.

Report destinations

Evidence wherever your cluster runs.

Remote destinations keep no local replica. The operator and CLI read the report when it is needed.

File

Local reports for development and simple self-hosted workflows.

./mirops-report.json

Amazon S3

Remote reports with IRSA support on EKS; read back on demand.

s3://reports/cluster.json

Azure Blob

Centralized evidence using Workload Identity on AKS.

azure://reports/cluster.json

PVC

The on-prem destination for clusters that keep evidence in Kubernetes storage.

pvc://mirops-reports/cluster.json

Open source

Start with one cluster.

mirops is Apache-2.0 and self-hosted today.

Available now

OSS

Everything needed to make upgrade readiness a repeatable engineering practice.

Freeself-hostedInstall
  • Operator, CLI, Headlamp plugin and Helm chart
  • Add-on compatibility for 10 common add-ons across Kubernetes 1.24–1.35
  • Dependency graph with propagated and per-namespace risk
  • SAFE / WARNING / CRITICAL verdicts and health score
  • Production and non-production profiles
  • File, S3, Azure Blob and PVC reports
  • Optional AI copilot (70% rules / 30% AI), always off by default

The mirops ecosystem

Operate on a mirror. Decide before you act.

mirops means mirror + ops: a model of the cluster where dependencies, compatibility and propagated risk are visible before a Kubernetes upgrade changes the live system.

OperatorBuilds the mirror, scores readiness and serves the report.
CLIRenders reports and enforces the gate in CI/CD.
Headlamp pluginShows the graph, verdict, findings and namespace risk.
Helm chartDeploys the operator on-prem, EKS or AKS.
Built byEnrique CruzFounderMario FloresCo-founder

Install the open source stack

Ready to make upgrade risk visible?

Install the chart, apply an UpgradeAnalysis, then use the CLI wherever you already run CI.

View on GitHubBack to product
# install the operator
helm install mirops \
  oci://ghcr.io/miropshq/charts/mirops \
  --version <v>

# create an analysis
kubectl apply -f upgrade-analysis.yaml

# gate a release
mirops scan --source ./mirops-report.json --enforce