Create ocs-operator test configuration bundle

[rocrisp]

Summary

Create the first test configuration bundle for ocs-operator as a proof-of-concept, following the bundle spec defined in issue #1.

Details

Research the ocs-operator CRD schema and create the following files under bundles/ocs-operator/:

Files to create

1. metadata.yaml — Machine-readable contract:

   • Operator name, channel (stable), namespace (openshift-storage), catalogSource
   • Hardware requirements (if any)
   • Health check conditions (StorageCluster Ready status)
   • Known issues section
   • Diagnostics/must-gather image

2. 01-operand-crs.yaml — Custom Resources to deploy OCS operands:

   • Minimal StorageCluster CR
   • Any other required CRs for basic operand deployment

3. 02-validate.sh — Validation script:

   • Wait for StorageCluster to reach Ready phase
   • Check that OCS pods are running
   • Accept namespace as $1 argument
   • Exit 0 on success, non-zero on failure
   • Must be executable

4. 00-prerequisites.yaml — Prerequisites (if needed):

   • Any required ConfigMaps, Secrets, RBAC, or namespace setup

5. teardown.yaml — Cleanup resources:

   • Delete the StorageCluster CR and any other created resources

Acceptance Criteria

• All bundle files created under bundles/ocs-operator/
• 02-validate.sh is executable and exits 0 when operands are healthy
• metadata.yaml follows the schema from issue Create a plan based on this documentation #1
• Bundle can be applied manually: oc apply -f 01-operand-crs.yaml

Depends on

• Set up repo structure and operator mapping file #2 (repo structure)

Parent Epic

Test Configuration Bundle for Certsuite Operand Installation