Merge branch 'feature/traefik-proxy-fully-integrates-with-hashicorp-nomad' into 'master'

traefik on nomad, adding docs, screenshots

See merge request all-staff/hashiqube!93

Author: Riaan Nolan

Vagrantfile

@@ -72,6 +72,8 @@ Vagrant::configure("2") do |config|
       if machines.size == 1 # only expose these ports if 1 machine, else conflicts
         config.vm.network "forwarded_port", guest: 8200, host: 8200 # vault
         config.vm.network "forwarded_port", guest: 4646, host: 4646 # nomad
+        config.vm.network "forwarded_port", guest: 8080, host: 8080 # nomad-traefik
+        config.vm.network "forwarded_port", guest: 8181, host: 8181 # nomad-traefik-admin
         config.vm.network "forwarded_port", guest: 19702, host: 19702 # waypoint-kubernetes-minikube
         config.vm.network "forwarded_port", guest: 9702, host: 9702 # waypoint-nomad
         config.vm.network "forwarded_port", guest: 19200, host: 19200 # boundary

hashicorp/README.md

@@ -939,6 +939,78 @@ Bringing machine 'user.local.dev' up with 'virtualbox' provider...
 ```
 ![Nomad](images/nomad.png?raw=true "Nomad")
 
+## Traefik Load Balancer for Nomad
+https://traefik.io/blog/traefik-proxy-fully-integrates-with-hashicorp-nomad/ <br />
+https://doc.traefik.io/traefik/v2.8/providers/nomad/
+
+We are thrilled to announce the full integration of the new Nomad built-in Service Discovery with Traefik Proxy. This is a first-of-its-kind ingress integration that simplifies ingress in HashiCorp Nomad. Utilizing Nomad directly with Traefik Proxy has never been so easy!
+
+In early May, Hashicorp announced Nomad Version 1.3. Among other updates, it also includes a nice list of improvements on usability and developer experience. Before this release, when using service discovery with Nomad, Traefik Proxy users had to use Hashicorp Consul and Nomad side-by-side in order to benefit from Traefik Proxy’s famous automatic configuration. Now, Nomad has a simple and straightforward way to use service discovery built-in. This improves direct usability a lot! Not only in simple test environments but also on the edge.
+
+`http://localhost:8080/` and `http://localhost:8181`
+
+![Traefik Load Balancer](images/traefik-dashboard.png?raw=true "Traefik Load Balancer")
+
+![Traefik Load Balancer](images/traefik-proxy.png?raw=true "Traefik Load Balancer")
+
+`vagrant up --provision-with nomad --provider docker`
+
+The new native Service Discovery in Nomad really does work seamlessly. With this integration, delivering load balancing, dynamic routing configuration, and ingress traffic routing become easier than ever. Check out the Traefik Proxy 2.8 Release Candidate and the Nomad 1.3 release notes.
+
+`curl -H "Host: whoami.nomad.localhost" http://localhost:8080 -v`
+
+```
+*   Trying 127.0.0.1:8080...
+* Connected to localhost (127.0.0.1) port 8080 (#0)
+> GET / HTTP/1.1
+> Host: whoami.nomad.localhost
+> User-Agent: curl/7.79.1
+> Accept: */*
+> 
+* Mark bundle as not supporting multiuse
+< HTTP/1.1 200 OK
+< Content-Length: 365
+< Content-Type: text/plain; charset=utf-8
+< Date: Thu, 16 Jun 2022 02:08:56 GMT
+< 
+Hostname: 86bb7e3d366a
+IP: 127.0.0.1
+IP: 172.18.0.5
+RemoteAddr: 172.18.0.1:51192
+GET / HTTP/1.1
+Host: whoami.nomad.localhost
+User-Agent: curl/7.79.1
+Accept: */*
+Accept-Encoding: gzip
+X-Forwarded-For: 172.17.0.1
+X-Forwarded-Host: whoami.nomad.localhost
+X-Forwarded-Port: 80
+X-Forwarded-Proto: http
+X-Forwarded-Server: 5d7dc64220c8
+X-Real-Ip: 172.17.0.1
+
+* Connection #0 to host localhost left intact
+```
+## Fabio Load Balancer for Nomad
+https://github.com/fabiolb/fabio <br />
+https://fabiolb.net
+
+Fabio is an HTTP and TCP reverse proxy that configures itself with data from Consul.
+
+Traditional load balancers and reverse proxies need to be configured with a config file. The configuration contains the hostnames and paths the proxy is forwarding to upstream services. This process can be automated with tools like consul-template that generate config files and trigger a reload.
+
+Fabio works differently since it updates its routing table directly from the data stored in Consul as soon as there is a change and without restart or reloading.
+
+When you register a service in Consul all you need to add is a tag that announces the paths the upstream service accepts, e.g. urlprefix-/user or urlprefix-/order and fabio will do the rest.
+
+`http://localhost:9999/` and `http://localhost:9998`
+
+![Fabio Load Balancer](images/fabio.png?raw=true "Fabio Load Balancer")
+`vagrant up --provision-with nomad`
+
+Fabio runs as a Nomad job, see `hashicorp/nomad/jobs/fabio.nomad`
+Some routes are added via Consul, see `hashicorp/consul.sh`
+
 ## Consul
 https://www.consul.io/
 
@@ -1611,23 +1683,3 @@ Bringing machine 'hashiqube0.service.consul' up with 'virtualbox' provider...
     hashiqube0.service.consul: ++++ Login with admin:password
     hashiqube0.service.consul: /tmp/vagrant-shell: line 5:  5093 Terminated              sh -c 'sudo tail -f /var/log/boundary.log | { sed "/worker successfully authed/ q" && kill $$ ;}'
 ```
-
-## Fabio Load Balancer
-https://github.com/fabiolb/fabio <br />
-https://fabiolb.net
-
-Fabio is an HTTP and TCP reverse proxy that configures itself with data from Consul.
-
-Traditional load balancers and reverse proxies need to be configured with a config file. The configuration contains the hostnames and paths the proxy is forwarding to upstream services. This process can be automated with tools like consul-template that generate config files and trigger a reload.
-
-Fabio works differently since it updates its routing table directly from the data stored in Consul as soon as there is a change and without restart or reloading.
-
-When you register a service in Consul all you need to add is a tag that announces the paths the upstream service accepts, e.g. urlprefix-/user or urlprefix-/order and fabio will do the rest.
-
-`http://localhost:9999/` and `http://localhost:9998`
-
-![Fabio Load Balancer](images/fabio.png?raw=true "Fabio Load Balancer")
-`vagrant up --provision-with nomad`
-
-Fabio runs as a Nomad job, see `hashicorp/nomad/jobs/fabio.nomad`
-Some routes are added via Consul, see `hashicorp/consul.sh`

hashicorp/images/traefik-dashboard.png

@@ -122,6 +122,10 @@ cd /vagrant/hashicorp/nomad/jobs;
 #nomad run --address=http://localhost:4646 countdashboardtest.nomad
 nomad plan --address=http://localhost:4646 fabio.nomad
 nomad run --address=http://localhost:4646 fabio.nomad
+nomad plan --address=http://localhost:4646 traefik.nomad
+nomad run --address=http://localhost:4646 traefik.nomad
+nomad plan --address=http://localhost:4646 traefik-whoami.nomad
+nomad run --address=http://localhost:4646 traefik-whoami.nomad
 # curl -v -H 'Host: fabio.service.consul' http://${VAGRANT_IP}:9999/
 echo -e '\e[38;5;198m'"++++ Nomad http://localhost:4646"
 }

hashicorp/images/traefik-proxy.png

@@ -0,0 +1,41 @@
+# https://traefik.io/blog/traefik-proxy-fully-integrates-with-hashicorp-nomad/
+
+job "traefik-whoami" {
+  datacenters = ["dc1"]
+
+  type = "service"
+
+  group "traefik-whoami" {
+    count = 1
+
+    network {
+       port "http" {
+         to = 8080
+       }
+    }
+
+    service {
+      name = "traefik-whoami"
+      port = "http"
+      provider = "nomad"
+
+      tags = [
+        "traefik.enable=true",
+        "traefik.http.routers.http.rule=Host(`whoami.nomad.localhost`)",
+      ]
+    }
+
+    task "server" {
+      env {
+        WHOAMI_PORT_NUMBER = "${NOMAD_PORT_http}"
+      }
+
+      driver = "docker"
+
+      config {
+        image = "traefik/whoami"
+        ports = ["http"]
+      }
+    }
+  }
+}

hashicorp/nomad.sh

@@ -0,0 +1,41 @@
+# https://traefik.io/blog/traefik-proxy-fully-integrates-with-hashicorp-nomad/
+
+job "traefik" {
+  datacenters = ["dc1"]
+  type        = "service"
+
+  group "traefik" {
+    count = 1
+
+    network {
+      port  "http"{
+         static = 8080
+      }
+      port  "admin"{
+         static = 8181
+      }
+    }
+
+    service {
+      name = "traefik-http"
+      provider = "nomad"
+      port = "http"
+    }
+
+    task "server" {
+      driver = "docker"
+      config {
+        image = "traefik:v2.8.0-rc1"
+        ports = ["admin", "http"]
+        args = [
+          "--api.dashboard=true",
+          "--api.insecure=true", ### For Test only, please do not use that in production
+          "--entrypoints.web.address=:${NOMAD_PORT_http}",
+          "--entrypoints.traefik.address=:${NOMAD_PORT_admin}",
+          "--providers.nomad=true",
+          "--providers.nomad.endpoint.address=http://10.9.99.10:4646" ### IP to your nomad server 
+        ]
+      }
+    }
+  }
+}