Skip to content
This repository has been archived by the owner on Jun 11, 2019. It is now read-only.

configure k8s traefik to handle non-k8s backends #3

Closed
billimek opened this issue May 31, 2018 · 2 comments
Closed

configure k8s traefik to handle non-k8s backends #3

billimek opened this issue May 31, 2018 · 2 comments

Comments

@billimek
Copy link
Owner

See https://docs.traefik.io/user-guide/kubernetes/#forwarding-to-externalnames
@billimek
Copy link
Owner Author

billimek commented Jun 2, 2018

Got this working but it requires pointing to an experimental recent build of traefik as the capability to properly do this was just added 11 days ago and isn’t in a release yet.

More details to follow

@billimek
Copy link
Owner Author

billimek commented Jun 2, 2018

It requires adding the following to the traefik_values.yaml file for the custom traefik helm chart:

image: containous/traefik
imageTag: c37b040217435c1f1683fa7466b6d4ac3002d878

the imageTag: c37b040217435c1f1683fa7466b6d4ac3002d878 represents the custom docker build of the commit sha with the bugfix for PR traefik/traefik#3231.

billimek added a commit that referenced this issue Jun 3, 2018
@billimek
Merge pull request #9 from billimek/chore/3
1587c77 
Fixes #3 - configure k8s traefik to handle non-k8s backends
This was referenced Jun 3, 2018
Closed
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@billimek