bitforge/orchard
3
0
Fork 0
Code Projects Wiki Activity

Fix Helm chart: rename minio.ingress to minioIngress to avoid subchart conflict

Browse Source 
The minio.ingress config was conflicting with the Bitnami MinIO subchart's
own ingress configuration, causing coalesce.go warnings. Renamed to
minioIngress as a top-level config.

Also enabled minioIngress by default with host minio-orch-dev.common.global.bsf.tools
This commit is contained in:
Mondo Diaz
2025-12-16 12:28:49 -06:00
parent 994f166de8
commit 11131c2071
6 changed files with 39 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
README.md
View File

@@ -553,19 +553,18 @@ orchard:
presignedUrlExpiry: 3600
# MinIO ingress (required for presigned URL downloads)
minio:
ingress:
minioIngress:
enabled: true
className: "nginx"
annotations:
cert-manager.io/cluster-issuer: "letsencrypt"
host: "minio.your-domain.com"
tls:
enabled: true
className: "nginx"
annotations:
cert-manager.io/cluster-issuer: "letsencrypt"
host: "minio.your-domain.com"
tls:
enabled: true
secretName: minio-tls
secretName: minio-tls
```
When `minio.ingress.enabled` is `true`, the S3 endpoint automatically uses the external URL (`https://minio.your-domain.com`), making presigned URLs accessible to external clients.
When `minioIngress.enabled` is `true`, the S3 endpoint automatically uses the external URL (`https://minio.your-domain.com`), making presigned URLs accessible to external clients.
See `helm/orchard/values.yaml` for all configuration options.