Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add provider specific cnameFlattening Trigger #4032

Open
gamalan opened this issue Oct 12, 2018 · 0 comments
Open

Add provider specific cnameFlattening Trigger #4032

gamalan opened this issue Oct 12, 2018 · 0 comments
Labels
kind/enhancement a new or improved feature. priority/P3 maybe

Comments

@gamalan
Copy link
Contributor

gamalan commented Oct 12, 2018

Do you want to request a feature or report a bug?

Feature (as per @nmengin suggestion, moved from PR #3843)

What did you expect to see?

Add provider specific cnameFlattening Trigger.

traefik.frontend.cnameFlattening
traefik.ingress.kubernetes.io/cname-flattening

To enable cnameFlattening only for a specific provider. But keep global if needed. Theoretically, it should only be enabled for a specific service.

This addressing PR #3403, by default when cnameFlattening is enabled, it will check for all route. After some thinking/testing again, although the record is being cached, it should not necessarily check all service.

If approved, then traefik-extra-service-fabric need to be updated as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement a new or improved feature. priority/P3 maybe
Projects
None yet
Development

No branches or pull requests

3 participants