feat: add multi-ingress support documentation #174
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves portainer/k8s#173
Summary
ingress
key.ingress
can be either a single object (legacy behavior) or an array (for multiple Ingress resources).Details
ingress
is an array, each entry results in a separate Ingress resource (e.g., for HTTP and HTTPS, or multiple hosts).ingress
is a map/object, the chart behaves as before, creating a single Ingress resource.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.