feat: Add overrides for ingress backend service name and port #869
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.
This change adds support for overriding the ingress backend service name and port via the serviceName and servicePort values while keeping the existing defaults.
These overrides are required to support AWS ALB “action” annotations such as:
In these cases, the ingress backend must reference a logical action name instead of a real Kubernetes Service:
Without the ability to override serviceName and servicePort, such ALB action backends cannot be expressed through the chart values.