You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would you like to be added?
I’d like the Portainer Helm chart to support defining multiple Kubernetes Ingress resources, so operators can, for example, have both HTTP (port 8000) and HTTPS (port 9443) Ingresses—or multiple host-based Ingresses—without having to deploy the chart twice.
Why is this needed?
Currently the chart’s values.yaml only allows a single .ingress block. In environments where you need separate listeners, SSL redirect rules, path mappings, or distinct hostnames, maintaining two separate releases of the chart is cumbersome and error-prone.
Values schema supports a top-level ingresses array
Each entry renders its own Ingress resource named {{ .Release.Name }}-{{ .Values.ingresses[i].name }}
Backward-compatibility: if ingresses is unset but ingress is present, chart behaves as it does today
Additional context
This would allow a single Helm release to manage multiple ALB listeners (or other controllers) cleanly, without duplicating values or releases.
The text was updated successfully, but these errors were encountered:
Feature request
What would you like to be added?
I’d like the Portainer Helm chart to support defining multiple Kubernetes Ingress resources, so operators can, for example, have both HTTP (port 8000) and HTTPS (port 9443) Ingresses—or multiple host-based Ingresses—without having to deploy the chart twice.
Why is this needed?
Currently the chart’s
values.yaml
only allows a single.ingress
block. In environments where you need separate listeners, SSL redirect rules, path mappings, or distinct hostnames, maintaining two separate releases of the chart is cumbersome and error-prone.Proposed Values API
Extend
values.yaml
from:to something like:
Acceptance criteria
Values schema supports a top-level ingresses array
Each entry renders its own Ingress resource named {{ .Release.Name }}-{{ .Values.ingresses[i].name }}
Backward-compatibility: if ingresses is unset but ingress is present, chart behaves as it does today
Additional context
This would allow a single Helm release to manage multiple ALB listeners (or other controllers) cleanly, without duplicating values or releases.
The text was updated successfully, but these errors were encountered: