> Rather than being pre-compiled and linked, however, plugins are executed on the fly by Yaegi, an embedded Go interpreter. Woof, no thank you. Go is basically incompatible with any kind of plugin-like dynamic linking. There are basically two reasonable models for doing something like plugins: the HashiCorp model, where plugins are actually separate processes that do some kind of intra-process communication with the…
Traefik, Now With Native Go Plugins
11–20 of 65 posts
Re: Traefik, Now With Native Go Plugins
#12Re: Traefik, Now With Native Go Plugins
#13I've been wanting to use Traefik for a long time but there's this security issue[0] that's almost two(!) years old now that's been keeping me from deploying it in production. As far as I can tell, there's still no out-of-the-box solution that's not overly complicated and won't come back to haunt me a year or two from now. [0] https://github.com/traefik/traefik/issues/4174 [1] https://doc.traefik.io/traefik/providers/…
https://github.com/Tecnativa/docker-socket-proxy
https://github.com/traefik/traefik/issues/4174#issuecomment-
Create a private network that only connects Traefik and the proxy, and limit Traefik's access to only the GET requests it needs to operate. Now the socket is only exposed to a local container.
Re: Traefik, Now With Native Go Plugins
#14I've been wanting to use Traefik for a long time but there's this security issue[0] that's almost two(!) years old now that's been keeping me from deploying it in production. As far as I can tell, there's still no out-of-the-box solution that's not overly complicated and won't come back to haunt me a year or two from now. [0] https://github.com/traefik/traefik/issues/4174 [1] https://doc.traefik.io/traefik/providers/…
This security issue is not that simple to manage as you probably know. It's mainly due to the fact that there is now way to have authorization on the the docker API. This is not the case on Kubernetes for example where you have RBAC to prevent this kind of issue. We have described this in detail in our documentation, and you have many solutions/workarounds to address this: https://doc.traefik.io/traefik/providers/doc…
The only solution I've seen/used that wasn't convoluted or brittle is running a little daemon to just shovel container metadata into Consul and going from there.
Re: Traefik, Now With Native Go Plugins
#15I would _really_ like to see social auth middleware (something like authelia, but simpler to setup and deploy, especially as an ingress).
Re: Traefik, Now With Native Go Plugins
#16Quick question: is this the beginning of monetization of some of traefik future features ?
Re: Traefik, Now With Native Go Plugins
#17> Rather than being pre-compiled and linked, however, plugins are executed on the fly by Yaegi, an embedded Go interpreter. Woof, no thank you. Go is basically incompatible with any kind of plugin-like dynamic linking. There are basically two reasonable models for doing something like plugins: the HashiCorp model, where plugins are actually separate processes that do some kind of intra-process communication with the…
Re: Traefik, Now With Native Go Plugins
#18I would _really_ like to see social auth middleware (something like authelia, but simpler to setup and deploy, especially as an ingress).
Re: Traefik, Now With Native Go Plugins
#19I don't really have any interest in plugins personally, but this is still quite an amazing project.