Hacker News Reader

Comment by snorremd | Hacker News Reader

Træfik works pretty well as an automated https proxy as well: https://traefik.io/ It is still missing a caching feature though, so it might not be a good fit for everyone. It has a Docker backend which works with Docker labels (much the same way the https-portal project uses environment vars).

View on HN

Traefik is really cool for most usage, I tried to used it in production and here are some of the shortcoming I found (the 2 first issues are on github):

- If you use DNS for a blue-green deployment, traefik does not honor DNS ttls (because it uses the DNS of go and go might do some caching) so when you do the switch you might still end on the "old" environment

- An error on one of the cool feature: serving error page when your backend returns some HTTP code

- Some configuration options are not documented (but easily found using github search)

I still love this software and I will keep looking at it.

By default, go compiles binaries linked to libc to use the system DNS resolver. It does re-implement a DNS resolver but it's only used if CGO is disabled at compilation time.

That's only half right. It does link to libc, but the default behavior on linux is to use Go unless some conditions are met.

Use go for what? DNS resolution? The default behavior is to use the system DNS resolver. The Go resolver will be used if the system is resolver is not avaialble (e.g. if the binary is compiled as pure go) or if the net.Resolver has the PreferGo flag set (which is false by default).

https://github.com/golang/go/blob/541f9c0345d4ec52d9f4be5913...

Is it possible for me to dynamically configure Traefik for non-Docker environments? I would like to run a Traefik instance which acts as a https-proxy for arbitrary domains,hosts and ports - without having to restart at all.

I would ALSO like to run a Traefik instance which acts as a https-proxy for arbitrary domains,hosts and ports - without having to restart at all.

As long as you're using one of the dynamic backends that Traefik hooks into, such as Consul for example, you can do this pretty easily.

I do this exact thing with Traefik, Consul, and some various miscellaneous services that don't fall under the dynamically-discovered umbrella when they might run under k8s or nomad. I write a value to Consul with the desired Host: match, a backend server to route requests to, and Traefik will handle routing to any backend server it can reach without restarts or interrupting service.

We are using Traefik with k8s with great success in production. They start to provide commercial support, which is great for enterprise.

Reply on news.ycombinator.com