exercise_cluster

You can identify and reproduce operator bugs by deploying cluster fixtures, applying mutation scenarios with kubectl, and validating the cluster health with an observer to triage failures across lifecycle, config, topology, and failure scenarios.

End-to-end mutation testing involves deploying cluster fixtures, applying real mutation scenarios, and verifying health metrics with an observer to triage bugs across lifecycle, config, topology, and failure scenarios.

Yes, running Multigres exercises requires kubectl access to a Kind or EKS cluster, a configured observer, and fixture prerequisites to successfully drive reconciliations and collect health metrics.

You validate observer health metrics after applying cluster mutations by running the exerciser against Multigres fixtures, which collects health metrics and generates structured reports for debugging and bug triage.

The best way to reproduce operator bugs in lifecycle and topology scenarios is to deploy Multigres fixtures, apply targeted mutations, and use the observer to verify end-to-end health and generate structured debugging reports.

If Multigres fixture reconciliations are not working during mutation testing, you likely lack proper kubectl access, a configured observer, or the required fixture prerequisites needed to drive end-to-end mutations.