Ultimately, in Traefik, you configure HTTPS on the router level. So, no certificate management yet! General Concepts To avoid confusion, let’s state the obvious - We haven’t yet configured anything but enabled requests on 443 to be handled by Traffic. "443:443" #Docker sends requests on port 443 to Traefik on port 443 =:443 #Declares the web-secure entrypoint in Traefik Image: containous/whoami:v1.3.0 Getting Things Readyįirst things first, let’s make sure our setup can handle HTTPS traffic on the default port ( :443), and that Traefik listens to this port thanks to an entrypoint we’ll name web-secure. "/var/run/docker.sock:/var/run/docker.sock:ro" We’ll assume you have a basic understanding of Traefik on Docker and that you’re familiar with its configuration (if not, it’s time to read Traefik 2 & Docker 101).ĭuring this article, we’ll use my pet demo docker-compose file: it enables the docker provider and launches a my-app application that allows us to test any request. The challenge we’ll accept is the following - You have an HTTP service exposed through Traefik, and you want Traefik to deal with the HTTPS burden (TLS termination), leaving your pristine service unspoiled by mundane technical details. Luckily for us, Traefik tends to lower this kind of hurdle and makes sure that there are easy ways of securely connecting your developments to the outside world. Such a barrier can be encountered when dealing with HTTPS and its certificates.
Yes, especially if they don’t involve real-life practical situations.īut these superpowers are sometimes hindered by tedious configuration work that expects you to master yet another arcane language assembled with heaps of words you’ve never seen before.
There are hundreds of reasons why I love being a developer (besides memories of sleepless nights trying to fix a video game that nobody except myself would ever play).īeing a developer gives you superpowers - you can solve any kind of problems.
0 kommentar(er)
