[ADD] Add traefik support #987
Open
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.
Summary
This PR adds optional support for Traefik by introducing a new IngressRoute template.
Charts can now render either a standard Kubernetes Ingress or a Traefik IngressRoute, depending on configuration.
Key Changes
Added ingress_route.yaml to render a traefik.io/v1alpha1 IngressRoute when ingress.traefik.enabled = true.
Updated ingress.yaml to render only when Traefik is disabled.
Extended values.yaml with:
Added fallback logic for service name and port, with clear failures when missing.
Why
Allows deployments using Traefik to work natively with its CRDs while keeping full backward compatibility for environments using standard Ingress controllers.
Compatibility
No breaking changes.
Existing setups using NGINX or other Ingress controllers continue working without modifications.