Skip to content

feat: add multi-ingress support documentation#174

Open
myk0la-b wants to merge 1 commit intoportainer:masterfrom
myk0la-b:feature/add-multi-ingress-support
Open

feat: add multi-ingress support documentation#174
myk0la-b wants to merge 1 commit intoportainer:masterfrom
myk0la-b:feature/add-multi-ingress-support

Conversation

@myk0la-b
Copy link

@myk0la-b myk0la-b commented May 14, 2025

Resolves portainer/k8s#173

Summary

  • The Helm chart now supports defining multiple Kubernetes Ingress resources using the existing ingress key.
  • ingress can be either a single object (legacy behavior) or an array (for multiple Ingress resources).
  • The chart template logic and documentation have been updated accordingly.
    Details
  • If ingress is an array, each entry results in a separate Ingress resource (e.g., for HTTP and HTTPS, or multiple hosts).
  • If ingress is a map/object, the chart behaves as before, creating a single Ingress resource.
  • All documentation and examples in README.md and values.yaml have been updated to reflect this change.
  • Chart version bumped to 1.0.67.
    Why?
    This change allows users to manage multiple Ingress resources (e.g., for different ports, hosts, or controllers) in a single Helm release, improving flexibility and maintainability.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feature request: add support for multiple Ingress definitions

1 participant