Repository navigation
[seaweedfs] S3 ingress hardcoded to tenant-root instead of using tenant's ingress #2399
Description
What this issue is about
The SeaweedFS filer external ingress in packages/extra/seaweedfs/templates/ingress.yaml has ingressClassName hardcoded to tenant-root instead of dynamically using the tenant's own ingress controller value.
Problem
In packages/extra/seaweedfs/templates/ingress.yaml, the ingressClassName is hardcoded:
```yaml
spec:
ingressClassName: tenant-root
```
The file already reads the correct ingress class from the namespace values at the top:
```yaml
{{- $ingress := .Values._namespace.ingress }}
```
But this $ingress variable is never used in the spec.
Expected behavior
The ingressClassName should use the tenant's ingress controller, just like other apps (e.g., Harbor) do:
```yaml
spec:
ingressClassName: {{ $ingress }}
```
This matches the pattern used across packages/apps/ (e.g., packages/apps/harbor/templates/ingress.yaml).
Impact
Tenants that have ingress: true (i.e., they have their own dedicated ingress controller) cannot route SeaweedFS filer/S3 traffic through their own ingress controller — traffic is always routed through the root tenant's ingress instead. This breaks ingress isolation for multi-tenant deployments.
Activity
dosubot commentedon Jul 27, 2026
Hi, myasnikovdaniil. I'm Dosu, and I'm helping the cozystack team manage their backlog and am marking this issue as stale.
Issue Summary
ingressClassName: tenant-root.{{ $ingress }}instead, matching the behavior used by other app templates.Next Steps
Thanks for your understanding and contribution.