Support traefik.backend for ECS
#3510
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hwhelan-CB
changed the title
ldez
added
kind/enhancement
hwhelan-CB
changed the title
ldez
changed the title
traefik.backend
|
Using the
|
ldez
changed the title
traefik.backendtraefik.backend for ECS
Use BackendName label to allow different backend versions to exist without creating a new Backend for each service.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
Uses the Traefik
traefik.backendto allow two different versions of the same ECS service to exist without Traefik creating a separate frontend and backend for each. This makes canary deployments with ECS possible with Traefik, as two different versions of the same ECS service can be load-balanced between by existing as one Traefik backend and associating with one frontend.Motivation
Canary deployments. Currently canary deployments with ECS and Traefik are not possible because the
traefik.backendis ignored. If two versions of the same ECS service are created, two Traefik backends and frontends are created. This fix allows the use of thetraefik.backendto indicate that two services belong to the same backend.More
Additional Notes
Related issue: #1164