Fix S3 adapter 502 timeout — gateway was connecting to MinIO on wrong port.
Root cause
MinIO ClusterIP service minio listens on port 80 (targetPort 9000). Config had :9000 which is only on the headless service minio-cluster-hl. Gateway connected to ClusterIP:9000, got no response, timed out at 30s, returned 502.
Already applied live, this commit captures it in git.
## Summary
Fix S3 adapter 502 timeout — gateway was connecting to MinIO on wrong port.
## Root cause
MinIO ClusterIP service `minio` listens on **port 80** (targetPort 9000). Config had `:9000` which is only on the headless service `minio-cluster-hl`. Gateway connected to ClusterIP:9000, got no response, timed out at 30s, returned 502.
## Changes
| File | Change |
|------|--------|
| `configmap.yaml` | S3 upstream `:9000` → `:80` |
| `gateway-config-secret.enc.yaml` | Same port fix (actual mounted config) |
| `network-policy.yaml` | Add port 80 egress to storage namespace |
## Verified
```
Before: curl X-Service:s3 → 502 (30s timeout)
After: curl X-Service:s3 → 403 AccessDenied (MinIO reached, auth issue separate)
```
Already applied live, this commit captures it in git.
MinIO ClusterIP service listens on port 80 (targetPort 9000).
Config had port 9000 which caused 30s timeout then 502 — gateway
connected to service port 9000 which doesn't exist on the ClusterIP.
Changes:
- configmap.yaml: S3 upstream :9000 → :80
- gateway-config-secret.enc.yaml: same
- network-policy.yaml: add port 80 egress to storage namespace
Verified: S3 adapter now reaches MinIO (403 AccessDenied = auth issue,
not connectivity).
rock
merged commit 5dd76f3b49 into main2026-09-08 17:03:55 +00:00
rock
deleted branch fix/s3-adapter-port2026-09-08 17:08:46 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Fix S3 adapter 502 timeout — gateway was connecting to MinIO on wrong port.
Root cause
MinIO ClusterIP service
miniolistens on port 80 (targetPort 9000). Config had:9000which is only on the headless serviceminio-cluster-hl. Gateway connected to ClusterIP:9000, got no response, timed out at 30s, returned 502.Changes
configmap.yaml:9000→:80gateway-config-secret.enc.yamlnetwork-policy.yamlVerified
Already applied live, this commit captures it in git.