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 #4134

Closed
wants to merge 7 commits into from
Closed

Add provider specific cnameFlattening Trigger #4134

wants to merge 7 commits into from

Conversation

gamalan
Copy link
Contributor

@gamalan gamalan commented Oct 30, 2018

What does this PR do?

Add provider specific cnameFlattening Trigger.

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

Motivation

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 again, although the record is being cached, it should not necessarily check all service.

More

  • Added/updated tests
  • Added/updated documentation

Additional Notes

If approved, then traefik-extra-service-fabric need to be updated as well.
Re add from PR #3843

# Conflicts:
#	docs/configuration/backends/consulcatalog.md
#	docs/configuration/backends/docker.md
#	docs/configuration/backends/ecs.md
#	docs/configuration/backends/marathon.md
#	docs/configuration/backends/mesos.md
#	docs/configuration/backends/rancher.md
#	provider/consulcatalog/config_test.go
#	provider/docker/config.go
#	provider/docker/config_container_docker_test.go
#	provider/ecs/config.go
#	provider/ecs/config_test.go
#	provider/kubernetes/kubernetes.go
#	provider/kv/keynames.go
#	provider/kv/kv_config.go
#	provider/label/names.go
#	provider/marathon/config_test.go
#	provider/mesos/config_test.go
#	provider/rancher/config.go
#	provider/rancher/config_test.go
#	types/types.go
@geraldcroes
Copy link
Contributor

Hi @gamalan!

Thank you for your contribution to the project, we're very grateful ... but at the same time we're embarrassed because we're not ready to merge your work. As we said in the latests release note , we're re-thinking some core aspects of Traefik. As a consequence, the code base has drastically changed (you can see for yourself the #4168 PR ... quite a refactoring).

Even though we cannot accept the PR right now, we would like to keep it in our radar.

I propose we close the current PR but keep #4032 open to ping you when the time comes.

WDYT?

@geraldcroes geraldcroes closed this Nov 8, 2018
@gamalan
Copy link
Contributor Author

gamalan commented Nov 8, 2018

@geraldcroes ah, I see. Okay then, I probably check other issues to solve.

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

Successfully merging this pull request may close these issues.

None yet

4 participants