Summary

When deploying the cost-onprem chart with MinIO as the S3 backend (instead of ODF), the ingress component fails to upload data to MinIO because it connects on port 80 (HTTP default) while the MinIO Service exposes port 9000.

Root Cause

Three compounding issues:

• deploy-minio-test.sh creates a MinIO Kubernetes Service on port 9000
• The Helm chart's INGRESS_MINIOENDPOINT env var receives only a hostname (no port) from the cost-onprem.storage.endpoint helper template
• The ingress Go application (minio-go SDK) defaults to port 80 when no port is specified

Additionally, install-helm-chart.sh was setting the unused costManagement.s3Endpoint Helm value instead of the odf.endpoint / odf.port / odf.useSSL values that templates actually consume.

Fix Applied

• deploy-minio-test.sh: Changed MinIO Service from port: 9000 to port: 80, targetPort: 9000 to align with HTTP default behavior
• install-helm-chart.sh: Corrected to set odf.endpoint, odf.port=80, odf.useSSL=false when MINIO_ENDPOINT is detected
• install-helm-chart.sh: Fixed credential lookup to parse MinIO namespace from FQDN and use correct secret key names (access-key/secret-key)
• install-helm-chart.sh: Switched bucket-setup pod image from alpine:latest (Docker Hub rate-limited) to registry.access.redhat.com/ubi9/ubi-minimal
• test_storage.py: Fixed S3 endpoint discovery to prioritize MASU pod's S3_ENDPOINT env var over ODF route (avoids false failures on clusters with both ODF and MinIO)
• New developer guide: docs/development/ocp-dev-setup-minio.md

Testing

• Full E2E suite (149 tests) passes with MinIO on the parodos-dev cluster
• Previously failing storage tests (3 failures) now pass after endpoint discovery fix
• Deployed and verified on stress.parodos.dev cluster

Affected Files

• scripts/deploy-minio-test.sh
• scripts/install-helm-chart.sh
• tests/suites/infrastructure/test_storage.py
• docs/development/ocp-dev-setup-minio.md (new)
• docs/operations/installation.md
• docs/development/README.md
• docs/README.md
• README.md