kubeblocks-engine-minio

What problem does it solve?

MinIO deployment on KubeBlocks often requires careful topology selection, version strategy, storage configuration, and preflight validation. This skill provides the primary create-time entry to standardize MinIO provisioning, reduce guesswork, and ensure a repeatable workflow.

Core Features & Use Cases

• Topology and sizing guidance: default distributed topology with production recommendations and dev/test adjustments.
• Version strategy and preflight: uses stable addon evidence and requires preflight when environment unknown.
• Minimal create path and validation: ensures a single-component manifest with proper PVCs and placement constraints, plus validation steps before handoff.
• Next hops and recovery: routes to lifecycle, observability, troubleshooting, and optional TLS/config adjustments.
• Forbidden routes: prevents routing create through generic engines to maintain trust in the dedicated MinIO engine.
• Evidence anchors: optional corroboration with addon evidence (examples/minio/cluster.yaml) for stronger runtime checks.

Quick Start

Draft the MinIO cluster manifest following the distributed topology default and apply it to your cluster.