Skip to main content

My traefik demo

I've been using haproxy as my reverse proxy for a while and it's hard not to like. The challenge for any production system is deploying new services and sometimes updates. One definite weakness is updating https certs. Keep in mind if you believe in configuration as code then haproxy and an all in one deploy might not be a bad thing but that could be applied to various dimensions in the "system".

For the purpose of discussion haproxy and traefik perform a similar function but where haproxy is static, traefik services register. Traefik has two killer features. [1] registration of dynamic services [2] dynamic wildcard support at let's encrypt.

PREREQUISITES

  • docker, docker-compose
  • docker-machine could be useful if you want to do remote deploys (post for another day)
  • dns + nameserver
  • traefik supported DNS service (I'm using digitalocean in this example)
  • at least one demo service


LAUNCH TRAEFIK

This was cobbled together from a number of sources...

$ mkdir -p /opt/traefik
$ cd /opt/traefik
$ touch acme.json docker-compose.yml traefik.toml
$ chmod 0600 acme.json

The acme file starts empty because traefik will fill it in with certs etc. The other two have some simple config. But first things first... create a docker network for the services to communicate with traefik.

$ docker network create web

The docker-compose.yml looks like this and is a standard compose file. The only interesting bits are the DO_AUTH_TOKEN which is configured at digital ocean and is used to update the DNS for let's encrypt. And the labels which are used by traefik and similar to passing environment variables into a container but more special purpose.

version: '3'

services:
  traefik:
    image: traefik
    command: --api --docker
    restart: always
    ports:
      - 80:80
      - 443:443
    networks:
      - web
    environment:
      - DO_AUTH_TOKEN=<token here>
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /opt/traefik/traefik.toml:/traefik.toml
      - /opt/traefik/acme.json:/acme.json
    labels:
      - "traefik.basic.frontend.rule=Host:traefik.ooc.systems"
    container_name: traefik

networks:
  web:
    external: true

The traefik.toml file can be used to stitch traefik and it's functions together as well as some basics for the user services. I have implemented the basic authentication feature in my traefic.toml but in reality the services are supposed to implement their own. Certainly if I were implementing a single signon solution integration right here would make sense along with some RBAC built into the apps/services. At the bottom of the file are the let's encrypt configuration items. That includes wildcard. (let's encrypt has some rate limits to beware)

debug = false

logLevel = "ERROR"
defaultEntryPoints = ["https","http"]

# openssl passwd -apr1 myPassword
[entryPoints]
  [entryPoints.http]
  address = ":80"
    [entryPoints.http.redirect]
    entryPoint = "https"
    [entryPoints.https.auth.basic]
      users = ["admin:passwd hash goes here"]
    [entryPoints.http.auth.basic]
      users = ["admin:passwd hash goes here"]
  [entryPoints.https]
  address = ":443"
  [entryPoints.https.tls]

[retry]

[docker]
endpoint = "unix:///var/run/docker.sock"
domain = "ooc.systems"
watch = true
exposedByDefault = false

[acme]
email = "my email addr here"
storage = "acme.json"
entryPoint = "https"
onHostRule = true
[[acme.domains]]        
  main = "*.ooc.systems"
  sans = ["ooc.systems"]
[acme.httpChallenge]
entryPoint = "http"
[acme.dnsChallenge]
  provider = "digitalocean"
  delayBeforeCheck = 0


Now that everything is configured... time to launch.

$ docker-compose up -d

At this point traefik is running; and it's time to launch a service.

$ mkdir -p $HOME/who
$ cd $HOME/who
$ touch docker-compose.yml

And here is the docker-compose.yml file.

version: "3"

services:
  app:
    image: emilevauge/whoami
    restart: always
    networks:
      - web
      - default
    expose:
      - "80"
    labels:
      - "traefik.docker.network=web"
      - "traefik.enable=true"
      - "traefik.basic.frontend.rule=Host:who.ooc.systems"
      - "traefik.basic.port=80"
      - "traefik.basic.protocol=http"

networks:
  web:
    external: true

Launching the service is as simple as

$ docker-compose up -d

NOTE this is not a docker swarm. That config is different and for another day but based on this config.

Comments

Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: http://www.eeti.com.tw/drivers_Linux.html (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the setup.sh answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…