<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Emile Vauge on Medium]]></title>
        <description><![CDATA[Stories by Emile Vauge on Medium]]></description>
        <link>https://medium.com/@emilevauge?source=rss-12234ecbea0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*eHv6W_GX-BThJlopQ7lStw.jpeg</url>
            <title>Stories by Emile Vauge on Medium</title>
            <link>https://medium.com/@emilevauge?source=rss-12234ecbea0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 03:55:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@emilevauge/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Announcing General Availability of Traefik Enterprise Edition]]></title>
            <link>https://medium.com/containous/announcing-general-availability-of-traefik-enterprise-edition-9c9aad363ce?source=rss-12234ecbea0------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c9aad363ce</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[traefikee]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[traefik]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Emile Vauge]]></dc:creator>
            <pubDate>Thu, 18 Apr 2019 11:21:00 GMT</pubDate>
            <atom:updated>2019-04-18T11:21:00.799Z</atom:updated>
            <content:encoded><![CDATA[<h4>Traefik Made Distributed</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dact8-guA9uxtevXzoeG8w.png" /></figure><p><a href="https://containo.us/"><em>Containous Inc</em></a>, the company behind the popular open source cloud native edge router, <a href="https://traefik.io/"><em>Traefik</em></a>, is proud to announce the general availability of Traefik Enterprise Edition, a new platform built on top of <em>Traefik</em>, designed for business-critical deployments.</p><p>In just three years, <em>Traefik</em>, the Cloud Native Edge Router, has become a key player in microservices infrastructures. With more than 21,000 stars on Github and 650,000,000 downloads on DockerHub, <em>Traefik</em> is widely used by major companies in their production environments.</p><p>In the latter part of 2018, Containous released <a href="https://blog.containo.us/introducing-traefik-enterprise-edition-83b78d09efeb">the early access of TraefikEE</a> to a select group of users, allowing them to refine the software. Today, Containous is proud to announce that TraefikEE has reached the <strong>1.0</strong> milestone, and is <strong>ready for production</strong>.</p><h3>Overview</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m1JK9SEsIIG8JFIfxPdz9Q.png" /></figure><p><em>TraefikEE</em> is built on top of <em>Traefik</em> and adds clustering features to satisfy the needs of enterprise customers. All <em>Traefik</em> concepts apply to <em>TraefikEE</em>, so if you’re already a <em>Traefik</em> user, you’re in familiar territory.</p><p>It runs on the edge of your platform to route the traffic to your applications, and is composed of two elements:</p><ul><li><strong>The data plane</strong>: horizontally scalable nodes, which forwards ingress traffic to your services</li><li><strong>The control plane</strong>: distributed nodes, implementing the raft consensus, which watch your platform and its services, store topology changes, and reconfigure the data plane to adapt ingress routing dynamically</li></ul><p>A <em>TraefikEE</em> cluster natively supports raft consensus between control nodes to safely store and replicate configurations. No external Key-Value Store nor third-party tool needed.</p><p>This distributed architecture is the cornerstone of <em>TraefikEE</em>’s strengths: natively <strong>highly available</strong>, <strong>scalable</strong> and <strong>secure</strong>.</p><p>Here is a 5 minute introduction video of <em>TraefikEE</em>:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FznFQLLGCB3U%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DznFQLLGCB3U&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FznFQLLGCB3U%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/ecda90df041a3a9e5ab467952585168b/href">https://medium.com/media/ecda90df041a3a9e5ab467952585168b/href</a></iframe><h3>Quickstart</h3><p>Start your free trial with TraefikEE today. Visit our website at <a href="https://containo.us/traefikee">https://containo.us/traefikee</a>, and get your trial license key in less than a minute!</p><p>Our <a href="https://docs.containo.us/">documentation</a> and our awesome CLI will help you bootstrap a TraefikEE cluster within a second. You can even <a href="https://containo.us/traefikee/#requestADemoModal">request a demo</a> on our website to set up a session with the core team.</p><p>Don’t hesitate to <a href="https://containo.us/traefikee/#contactUsModal">talk to our sales team</a>, they will find the best way to help your company deploying a powerful edge routing solution.</p><h3>Traefik Stays Open</h3><p><em>TraefikEE</em> is built on top of <em>Traefik</em>, that means that Traefik continues to evolve and will stay open source. Nothing changes! We are firm believers in open source, and <em>Traefik</em> will continue to be our main priority and a community-driven project. We are working on significant changes to Traefik, and <a href="https://blog.containo.us/back-to-traefik-2-0-2f9aa17be305">recently have shared details</a> on the <em>Traefik</em> 2.0 roadmap and released <a href="https://github.com/containous/traefik/releases/tag/v2.0.0-alpha4">the first alphas</a>. We won’t lie saying it’s going to be huge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w25VkQROXPgIzlJYaHtjww.png" /></figure><h3>About Containous Inc.</h3><p>Containous is the company that supports the development of Traefik, the popular open source cloud native edge router. Traefik is widely used around the globe with over 650 million downloads. Containous brings the future of software architecture by offering the most powerful tools to ease the deployment of your modern IT environments.</p><p>Find out more about Containous at <a href="https://containo.us/">containo.us</a> and follow <a href="https://twitter.com/containous">@containous</a> on Twitter.</p><p>With this new product, Containous continues to innovate and define new ways to access microservice platforms, pushing the limits of automation and scalability.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c9aad363ce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/containous/announcing-general-availability-of-traefik-enterprise-edition-9c9aad363ce">Announcing General Availability of Traefik Enterprise Edition</a> was originally published in <a href="https://medium.com/containous">containous</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Back to Traefik 2.0]]></title>
            <link>https://medium.com/containous/back-to-traefik-2-0-2f9aa17be305?source=rss-12234ecbea0------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f9aa17be305</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[announcements]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[traefik]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Emile Vauge]]></dc:creator>
            <pubDate>Tue, 19 Mar 2019 07:01:02 GMT</pubDate>
            <atom:updated>2019-03-19T07:01:02.515Z</atom:updated>
            <content:encoded><![CDATA[<h4>Gigawatts of Routing Power</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jnTKx4FOO4BMuYfo0oejXA.png" /></figure><p>Back in 2015, a revolution was under way. We were moving from manual, handcrafted infrastructures, to container-based, industrial, and human-free platforms. In those dark ages of orchestration, edge traffic was remarkably difficult to manage. On one side, we had traditional reverse-proxies that were built for static infrastructures, on the other side, we were building dynamic clusters made to deploy and manage thousands of microservices. The idea of having a simple and automatic edge router, all in one binary, was appealing, but also idealistic. The foundation of <a href="https://traefik.io/">Traefik</a> was laid that year, paving the way to building a project with strong values: <em>simplicity of configuration</em>, <em>modern features</em>, and <em>open to the community</em>. A few years later, the project has reached <a href="https://github.com/containous/traefik">21k stars on Github</a>, and more than 600 millions downloads. <em>Insane</em>.</p><p>Since then, the ecosystem around containers has changed a lot: Docker has become a de-facto standard, and Kubernetes has shown itself to be the clear winner in the battle for the best orchestration platform. Because of this, the <a href="https://landscape.cncf.io/">CNCF landscape</a> has exploded, with hundreds of components to choose from.</p><blockquote>The time has come to work on something new for Traefik.</blockquote><p>For several months, the maintainer team has been working on a deep refactoring of the codebase to provide the firm foundations for the next iteration of Traefik, and we are ready to share this vision with you.</p><p>Today, we’re announcing Traefik 2.0 alpha, the edge router built with the future in mind.</p><p>The new core is here, help us finalize Traefik with the features you want!</p><h3>We Want Features!</h3><p>Let’s see what we have in store.</p><h4>Vocabulary Clarification</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TMLGn4cDgUT5-8lCTyys_w.png" /></figure><p>Not a feature per se, but we still wanted to make it easier for newcomers to understand the core concepts at work in Traefik. We wanted every word to have a clear and unique meaning throughout the code and documentation.</p><p>Welcome p<em>roviders</em>, e<em>ntrypoints</em>, r<em>outers</em>, m<em>iddleware</em>, and s<em>ervices</em>.</p><ul><li><em>Providers</em> are the cluster technologies you already use (Kubernetes, Docker, Consul, Mesos, Rancher…). Traefik uses your provider’s API to discover the routes to your services.</li><li><em>Entrypoints</em>, in their most basic forms, are the open ports where requests will land.</li><li><em>Services</em> represent the software hosted on your infrastructure. Traefik knows how to deal with multiple instances of your programs (currently supporting multiple load balancing capabilities), and use the s<em>ervices</em> configuration to determine how to reach the actual program.</li><li><em>Routers</em> connect incoming requests to your s<em>ervices. </em>They<em> </em>hold<em> </em>the rules that decide which service handles the request.</li><li>Finally, pieces of <a href="https://docs.traefik.io/v2.0/middlewares/overview/"><em>middleware</em></a><em> </em>are components that may update the request before it is handled by a service. Out of the box, Traefik comes with middleware to manage authentication, rate limiting, circuit breaker, whitelisting, buffering, and so on.</li></ul><h4>Configuration Structure</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6JrXAXx86JLd9PkIPACB6Q.png" /></figure><p>Despite our best efforts, and because so many features have been added to Traefik since its first launch, we needed to polish things up and make sure every configuration option belonged in its place.</p><p>Here, it was a menial job that needed to be done, and we’ll spare you the details.</p><h3>Let Us Be Clear … We Want ACTUAL Features!</h3><p>So, let’s remove the mystery, since we’ve teased you enough. Here are the features we’ve added!</p><h4>TCP Support!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nF7c0J8WKGlAkIZlSzEeSA.png" /></figure><p>That’s right! It’s time to say goodbye to <a href="https://github.com/containous/traefik/issues/10">Issue #10</a>!</p><p>Yes, three years later, after <a href="https://github.com/containous/traefik/pull/4587">a lot of work</a> (<a href="https://github.com/containous/traefik/issues/10#issuecomment-142835077">as foretold</a>), and a lot of discussions, <a href="https://docs.traefik.io/v2.0/routing/routers/#configuring-tcp-routers">Traefik now fully supports the TCP protocol</a>.</p><p>Want to see an example? Let’s use the File Provider, and redirect every request on port27010 to your database service!</p><pre>[entrypoints]<br>   [entrypoints.web]<br>      address = &quot;:80&quot;</pre><pre>[entrypoints.mongo-port]<br>      address = &quot;:27017&quot;</pre><pre><strong>[tcp]</strong> # YAY!<br>   <strong>[tcp.routers]</strong><br>      <strong>[tcp.routers.everything-to-mongo]</strong><br>         entrypoints = [&quot;mongo-port&quot;]<br>         rule = &quot;HostSNI(`*`)&quot; <em># Catches every request</em>       <br>         service = &quot;database&quot;</pre><p>The best part? Traefik supports routing based on <a href="https://en.wikipedia.org/wiki/Server_Name_Indication">SNIs</a>!</p><pre>[entrypoints]<br>   [entrypoints.web]<br>      address = &quot;:80&quot;</pre><pre>[entrypoints.mongo-port]<br>      address = &quot;:27017&quot;</pre><pre>[tcp] # YAY!<br>   [tcp.routers]<br>      [tcp.routers.to-db-1]<br>         entrypoints = [&quot;mongo-port&quot;]<br>         <strong>rule = &quot;HostSNI(`db-1.domain`)&quot; </strong>      <br>         service = &quot;db-1&quot;<br>         <strong>[tcp.routers.to-db-1.tls]</strong> # The route is for TLS requests only</pre><pre>      [tcp.routers.to-db-2]<br>         entrypoints = [&quot;mongo-port&quot;]<br>         <strong>rule = &quot;HostSNI(`db-2.domain`)&quot;</strong>       <br>         service = &quot;db-2&quot;<br>         <strong>[tcp.routers.to-db-2.tls]</strong> # The route is for TLS requests only</pre><p>What’s even better? Traefik can go crazy, and support <em>both</em> HTTP <em>and</em> TCP on the <em>same</em> port.</p><blockquote>Yes, multiple protocols on the same entrypoint!</blockquote><pre>[entrypoints]<br>   [entrypoints.the-one]<br>      address = &quot;:443&quot;</pre><pre>[tcp]<br>   [tcp.routers]<br>      <strong>[tcp.routers.to-db-1]<br>         rule = &quot;HostSNI(`db-1.domain`)&quot;</strong>       <br>         service = &quot;db-1&quot;<br>         <strong>[tcp.routers.to-db-1.tls</strong>] # The route is for TLS requests only</pre><pre>[http]<br>   [http.routers]<br>      <strong>[http.routers.my-api]<br>         rule = &quot;Host(`api.domain`)&quot;  </strong>     <br>         service = &quot;my-api&quot;</pre><p>In its first alpha version, Traefik only enables TCP routes in the File Provider, but stay tuned because it will (very) soon be available for other providers!</p><h4>Middleware to Update the Requests</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NHKXX8kSbRlcUxMTWIu8_g.png" /></figure><p>Many features used to be magically embedded in Traefik, with room for customization but no option for fine-tuning.</p><p>Middlewares fill the gap and give you the possibility to enable/configure any feature you’d like, per router if you wish.</p><p>Middlewares are components that act on the request before it is actually forwarded to the services, and can even decide to <em>not</em> forward the request if a required condition isn’t met.</p><p>At release, Traefik comes with the following middlewares: <a href="https://docs.traefik.io/v2.0/middlewares/addprefix/">AddPrefix</a> (to add a prefix to the request path), <a href="https://docs.traefik.io/v2.0/middlewares/basicauth/">BasicAuth</a> &amp; <a href="https://docs.traefik.io/v2.0/middlewares/digestauth/">DigestAuth</a>, <a href="https://docs.traefik.io/v2.0/middlewares/forwardauth/">ForwardAuth</a> (to delegate authentication to a third-party service), <a href="https://docs.traefik.io/v2.0/middlewares/buffering/">Buffering</a>, <a href="https://docs.traefik.io/v2.0/middlewares/chain/">Chain</a> (to define reusable sets of middlewares), <a href="https://docs.traefik.io/v2.0/middlewares/circuitbreaker/">CircuitBreaker</a> (to avoid calling broken services), <a href="https://docs.traefik.io/v2.0/middlewares/compress/">Compress</a>, <a href="https://docs.traefik.io/v2.0/middlewares/errorpages/">Errors</a> (to provide custom error pages), <a href="https://docs.traefik.io/v2.0/middlewares/headers/">Headers</a>, <a href="https://docs.traefik.io/v2.0/middlewares/ipwhitelist/">IpWhitelist</a>, <a href="https://docs.traefik.io/v2.0/middlewares/maxconnection/">MaxConn</a> (to limit the number of simultaneous connections to a service), <a href="https://docs.traefik.io/v2.0/middlewares/passtlsclientcert/">PassTLSClientCert</a>, <a href="https://docs.traefik.io/v2.0/middlewares/ratelimit/">RateLimit</a> (to limit the number of requests to a service within a given period of time), <a href="https://docs.traefik.io/v2.0/middlewares/redirectregex/">RedirectRegex</a> and <a href="https://docs.traefik.io/v2.0/middlewares/redirectscheme/">RedirectScheme</a>, and <a href="https://docs.traefik.io/v2.0/middlewares/replacepath/">ReplacePath</a> (to update the query path before forwarding it to the service).</p><p>And more importantly, we’ve re-architectured the code to make it easier to provide additional middlewares in the near future.</p><h4>Kubernetes &amp; CRD</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*-vrBH4VaiOUvmcZrG3uDUw.png" /></figure><p>In the past two years, the community has been discussing (a lot) around “better ingress,” and looking at our previous Kubernetes provider, we agreed that there was room for improvement. With v2, it became obvious that if we wanted to let our Kubernetes fans benefit from every feature (like TCP and middleware) without being swarmed by a clutter of annotations, we had to propose an alternative.</p><p>Among the alternatives, <a href="https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/">CRD</a>s are more and more popular since they solve shortcomings of the ingress specification. Inspired by what Heptio did in Contour with <a href="https://github.com/heptio/contour/blob/master/docs/ingressroute.md">IngressRoute</a>, we extended the specification to implement every Traefik feature.</p><p>We firmly believe that a consensus can emerge from those proposals and lead to the next Ingress specification in Kubernetes.</p><p>Below is an example of this specification.</p><pre>apiVersion: traefik.containo.us/v1alpha1<br>kind: IngressRoute<br>metadata:<br>  name: test.crd<br>  namespace: default</pre><pre>spec:<br>  entrypoints:<br>    - web<br>    - web-secure</pre><pre>  routes:<br>    - match: Host(`traefik.io`) &amp;&amp; PathPrefix(`/foo`)<br>      kind: Rule<br>      services:<br>        - name: whoami1<br>          port: 80<br>          strategy: RoundRobin<br>      middlewares:<br>        - name: stripprefix<br>        - name: addprefix<br>          namespace: foo</pre><pre>    - match: Host(`containo.us`) &amp;&amp; Method(`POST`)<br>      kind: Rule<br>      services:<br>        - name: whoami2<br>          port: 80</pre><pre>  tls:<br>    secretName: supersecret</pre><h4>New Expressive Routing Rule Syntax</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0gwVmrBdOC7IADdLTF8qfg.png" /></figure><p>Traefik now supports an expressive syntax to define the router rules, with and, or, and parenthesis!</p><p>The available <a href="https://docs.traefik.io/v2.0/routing/routers/#rule">matchers</a> being Headers, HeadersRegexp, Host, HostRegexp, Method, Path, PathPrefix, and Query.</p><p>Since TCP is a whole different world, for now, it only supports a dedicated matcher: HostSNI.</p><p>Want to see examples?</p><pre>rule = (Host(`api.domain`) &amp;&amp; PathPrefix(`/v2`)) || Host(`api-v2.domain`)</pre><pre>rule = (Method(`DELETE`) || (Method(`POST`) &amp;&amp; Query(`action`, `delete`))) &amp;&amp; Host(&#39;api.domain&#39;)</pre><h4>Cross-Provider Support</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PRtbjY8TMGRbErnSt2gTkw.png" /></figure><p>Traefik has always been compatible with multiple providers, which is one of its greater strengths: whatever your infrastructure is, from bare metal to orchestrators and clusters, Traefik just works!</p><p>But with v2, we’ve gone a little further and allowed users to declare elements (middlewares, services, routers) in a provider, and to use them from a different one.</p><p>Let’s take a look at the following example, that declares an authentication middleware in a configuration file (the File Provider), which is being used from a Docker label (the Docker Provider).</p><pre># somewhere in a configuration file for the file provider<br>[http.middlewares.<strong>my-users</strong>.basicauth]<br>   users = [&quot;test:$apr1$H6uskkkW$IgXLP6ewTrSuBkTrqE8wj/&quot;, <br>            &quot;test2:$apr1$d9hr9HBB$4HxwgUir3HP4EsggP/QNo0&quot;]</pre><pre># somewhere in a docker compose file</pre><pre>your-container:<br>    image: your-docker-image</pre><pre>    labels:<br>      - &quot;traefik.http.routers.my-router.middlewares=file.<strong>my-users</strong>&quot;</pre><p>And of course, you could declare a router in a provider that points to services declared by another.</p><h4>TLS Termination per Route</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_sOVTxS-yCn-PDT9KdxHuw.png" /></figure><p>While adding TCP support to Traefik, we had to re-think almost everything, starting with the e<em>ntrypoint</em> itself — the very door to your cluster.</p><p>Our first idea was to dedicate e<em>ntrypoints</em> (and as a consequence port numbers) to a type of “protocol.” Unfortunately, in some cases, especially when people used Traefik to route requests for multiple clusters, we deemed it too restrictive. As a consequence, we allowed multiple protocols per e<em>ntrypoint</em>.</p><p>Then, as debates were still going on, we kept looking for ways to better control how users would configure TLS <em>termination</em> or <em>passthrough. </em>The idea of enabling TLS on the <em>Router</em> level won the brainstorming, and then passed the tests of proof of concept (we have <a href="https://github.com/juliens">quite a fan</a> of proof of concept branches on the team, to the point it has almost become a meme).</p><p>Here is an example with three routers listening on the same e<em>ntrypoint</em>, the first router terminates TLS connections (on HTTPS), the second router terminates TLS connections (on TCP), and the third router passes through, leaving the details of the TLS connection to be handled by the s<em>ervice </em>itself.</p><pre>[entrypoints]<br>   [entrypoints.web-secure]<br>      address = &quot;:443&quot;</pre><pre>[http]<br>   [http.routers.to-service-1]<br>      rule = &quot;Host(`domain-1`)&quot;<br>      service = &quot;service-1&quot;<br>      [http.routers.to-service-1.tls]<br>         # terminates the tls connection and sends clear data<br>         # to service 1</pre><pre>[tcp]<br>   [tcp.routers.to-service-2]<br>      rule = &quot;HostSNI(`domain-2`)&quot;<br>      service = &quot;service-2&quot;<br>      [tcp.routers.to-service-2.tls]<br>         # terminates the tls connection and sends clear data<br>         # to service 2</pre><pre>[tcp.routers.to-service-3]<br>      rule = &quot;HostSNI(`domain-3`)&quot;<br>      service = &quot;service-3&quot;<br>      [tcp.routers.to-service-3.tls]<br>         passthrough = true # sends encrypted data &quot;as is&quot; to service-3</pre><h4>Labels, Key-Value Configuration, Tags, …</h4><p>A small tweak on the surface, but quite an impact in the code, we’ve re-written the configuration parser. This new system ensures that every option in Traefik has the same path, whether expressed in TOML [something.that.is.here], a label attached to a container something.that.is.there, a key (as in key-value store) something/that/is/somewhere, or anything that might be available in the future.</p><h4>Revamped Documentation</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XCX8dtb6YNijHfzesntV6A.png" /></figure><p>We’ve updated the <a href="https://docs.traefik.io/v2.0">documentation</a> structure to help new users quickly understand how to use and configure Traefik. At the same time, we came up with an outline that mirrored the configuration structure, making it easier for expert users to learn more about specific configuration details.</p><h3>The Road to the Final Version</h3><p>Yes, more (<em>much</em> more) is on the way, but we were so eager to share the work that we couldn’t wait a minute longer than we already did.</p><blockquote>New WebUI, remaining providers, metrics, UDP, YAML, TLS stores &amp; options, canary, more documentation — everything is possible.</blockquote><p>Apart from re-enabling other providers (alpha comes with file, Docker, and k8s only), and enabling TCP for all of them (currently file only), the roadmap is full of features.</p><p>First, the most visible one, a contributor is actively working on a revamped WebUI, and from the mockups we saw, it looks <em>very</em> promising. We expect this new UI to help you navigate seamlessly through hundreds of routes.</p><p>Second, we’re working on improvements for TLS configuration, with stores and options, which will deserve its own explanation.</p><p>Third, now that we have tried our hand on a new protocol, well, we might as well add others (like UDP).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*4h5fssV0SEfpqLFzbNHVtg.png" /></figure><p>If you want to discuss or even help us implementing these features, please join us on <a href="https://slack.traefik.io/">Slack</a> or on <a href="https://github.com/containous/traefik">Github</a>, the maintainer team is always open to your contributions.</p><p>But the options don’t stop there — Traefik is a community-driven project, and we never know what is going to happen! We can’t wait to see what you’ll do with this new architecture.</p><h3>To be continued…</h3><blockquote>The community is at the center of our attention.</blockquote><p>We’ve scheduled an <a href="https://zoom.us/webinar/register/WN_4QohQ_mgTR6y8UVbjqqQ9g">online meet-up</a> where the maintainer team will exclusively talk about Traefik v2.0! If you were looking for an opportunity to ask questions or see a live demo, here it is.</p><p>Probably the most important, we <em>need</em> your feedback. Tell us what you think, voice your opinion! The alpha stage is the perfect timing to include disruptive changes. Go crazy with pull requests, tests, and ideas.</p><p>And finally, of course, our goal is to release the final as soon as possible!</p><blockquote>We hope you enjoy Traefik as much as we enjoy building it with you!</blockquote><p>Grab the <a href="https://github.com/containous/traefik/releases/tag/v2.0.0-alpha1">latest binaries</a> for Linux, Windows, and Mac on Github or get the official Docker image!</p><pre>docker pull traefik:v2.0.0-alpha1 (or 2.0.0-alpha1, v2.0, 2.0, faisselle)<br>docker pull traefik:v2.0.0-alpha1-alpine<br>docker pull traefik:v2.0.0-alpha1-nanoserver</pre><p>The documentation can be found on <a href="https://docs.traefik.io/v2.0/">https://docs.traefik.io/v2.0/</a> and the <em>huge</em> changelog is <a href="https://github.com/containous/traefik/blob/master/CHANGELOG.md#v200-alpha1-2019-03-18">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*UF-k6KGdXcUgnAsZBFsdYA.png" /></figure><p><em>Thank you </em><a href="https://medium.com/u/520ac88c453e"><em>Gérald Croës</em></a><em> for your major contribution on this blog post and congrats to all the team members that have been working so hard on this alpha release 👏</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f9aa17be305" width="1" height="1" alt=""><hr><p><a href="https://medium.com/containous/back-to-traefik-2-0-2f9aa17be305">Back to Traefik 2.0</a> was originally published in <a href="https://medium.com/containous">containous</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Traefik Enterprise Edition]]></title>
            <link>https://medium.com/containous/introducing-traefik-enterprise-edition-83b78d09efeb?source=rss-12234ecbea0------2</link>
            <guid isPermaLink="false">https://medium.com/p/83b78d09efeb</guid>
            <category><![CDATA[traefik]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[cloud-native]]></category>
            <dc:creator><![CDATA[Emile Vauge]]></dc:creator>
            <pubDate>Tue, 11 Dec 2018 14:01:00 GMT</pubDate>
            <atom:updated>2019-01-14T13:45:04.817Z</atom:updated>
            <content:encoded><![CDATA[<h4>We Made It Distributed</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AMCd3dCEjU7J9JbkIZnqow.png" /></figure><p><a href="https://containo.us/"><em>Containous</em></a>, the company behind <a href="https://traefik.io/"><em>Traefik</em></a>, is announcing Traefik Enterprise Edition — <em>TraefikEE</em> — a new platform built on top of <em>Traefik</em>, designed for business-critical deployments.</p><p>In just three years, <em>Traefik</em>, the Cloud Native Edge Router, has become a key player in microservices infrastructures. With more than 19,000 stars on Github and 400,000,000 downloads on DockerHub, <em>Traefik</em> is widely used by major companies in their production environments.</p><p>Today, we are proud to announce that <em>TraefikEE</em>, our new commercial product, has reached public beta. <em>TraefikEE</em> allows you to deploy distributed Traefik instances across your infrastructure, providing a scalable and reliable edge routing platform. Split into a control plane and a data plane, <em>Traefik</em> cluster nodes are easily deployed and operated using the <em>TraefikEE</em> CLI. Implementing the Raft consensus, <em>TraefikEE</em> can safely store and replicate configurations and TLS certificates across the nodes.</p><p>Let’s take a look at how <em>TraefikEE</em> works.</p><h3>TraefikEE — Overview</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rrzYD9rn8sjqwpqFsKatOQ.png" /><figcaption>TraefikEE Architecture</figcaption></figure><p><em>TraefikEE</em> is built on top of <em>Traefik</em> and adds clustering features to satisfy the needs of Enterprise customers. All <em>Traefik</em> concepts apply to <em>TraefikEE</em>, so if you’re already a <em>Traefik</em> user, you’re in familiar territory.</p><p>It runs on the edge of your platform to route the traffic to your applications, and is composed of two elements:</p><ul><li><strong>The data plane</strong>: horizontally scalable nodes, which forward ingress traffic to your services</li><li><strong>The control plane</strong>: distributed nodes, implementing the raft consensus, which watch your platform and its services, stores topology changes, and reconfigure the data plane to adapt ingress routing dynamically</li></ul><p>A <em>TraefikEE</em> cluster natively supports raft consensus between control nodes to safely store and replicate configurations. No external Key-Value Store nor third-party tool needed.</p><p>This distributed architecture is the cornerstone of <em>TraefikEE</em>’s strengths: natively <strong>highly available</strong>, <strong>scalable</strong> and <strong>secure</strong>.</p><h3><strong>Highly Available</strong></h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fbsl05RVuMtM%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dbsl05RVuMtM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fbsl05RVuMtM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c22c7c4f529eec0cb7720f989ea0212e/href">https://medium.com/media/c22c7c4f529eec0cb7720f989ea0212e/href</a></iframe><p>The control plane is a key component of <em>TraefikEE</em>. It is responsible for storing all cluster data, including events, TLS certificates, and <em>Traefik </em>configuration. It is also in charge of connecting to the orchestrator to generate the data plane routing configuration.</p><p>Since it is such a critical part of your system,<em> TraefikEE</em> is designed from the ground up to be fault tolerant: the control plane runs natively in cluster mode without any extra configuration or external Key Value Store. It ensures your data is always available and safe by using an internal distributed store, implemented with raft.</p><h3><strong>Scalable</strong></h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FYNKMcussMrM%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DYNKMcussMrM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FYNKMcussMrM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d7e3f6b8d924f1288acaae80f3fb3573/href">https://medium.com/media/d7e3f6b8d924f1288acaae80f3fb3573/href</a></iframe><p>The data plane is in charge of forwarding the incoming requests to the applications. It has been designed to scale horizontally at a glance in order to face irregular network loads.</p><p><em>TraefikEE</em> handles high loads in a blink: just add more nodes to the data plane to handle the additional requests. When the peak is gone, shrink the number of nodes to save resources. Of course, this process can be done automatically using auto-scaling tools.</p><h3><strong>Secure</strong></h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FrPAcKSiidUo%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DrPAcKSiidUo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FrPAcKSiidUo%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/ff7103e2f5fa243b346b3898e83d0c8d/href">https://medium.com/media/ff7103e2f5fa243b346b3898e83d0c8d/href</a></iframe><p>By splitting responsibilities between two components, <em>TraefikEE</em> follows the principle of “Separation of Concerns.”</p><p>To ensure that sensitive information only runs on a closed and safe environment, the control plane is not exposed to the outside. As a result, any malicious action from external traffic will stay stuck in the data plane and your platform will stay safe.</p><p>Moreover, <em>TraefikEE</em> only relies on encrypted communications between nodes, to add an extra layer of security.</p><h3><strong>Smooth Operations</strong></h3><p>Installing and managing a raft based application is usually a painful experience. Since <em>Traefik</em> was made popular thanks to its usability and refreshing user experience, we have extended those benefits to TraefikEE.</p><p>For this reason, <em>TraefikEE</em> comes with an additional CLI that manages to deploy and operate a cluster with several nodes in only one command line. Currently, Kubernetes and Docker Swarm Mode are supported. More platforms will be added soon. Teams will love to use this time-saving tool, <em>traefikeectl</em> (pronounced “traefikee-cuddle”).</p><p><em>TraefikEE</em> comes with a dashboard to visualize your cluster nodes configuration and status, in addition to aggregated data plane metrics.</p><p>Commercial support is bundled with TraefikEE. The Traefik engineering team immediately investigates and resolves any critical issues which may arise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WzNSFSmZijGcl2Gr_1s66A.png" /></figure><h3><strong>Early Access</strong></h3><p>TraefikEE is available in early access starting today. The registration process is as simple and automated as possible, so don’t fear endless registration forms nor crowded waiting queues before trying it out. Visit our website at <a href="https://containo.us/traefikee">https://containo.us/traefikee</a> and get your license key in less than a minute!</p><h3><strong>Traefik Stays Open</strong></h3><p><em>TraefikEE</em> is built on top of <em>Traefik</em>, that means that Traefik continues to evolve and will stay open source. Nothing changes! We are firm believers in open source, and <em>Traefik</em> will continue to be our main priority and a community-driven project. We are working on significant changes to Traefik, and <a href="https://blog.containo.us/traefik-spoiler-season-episode-1-3dbcb1f5d8b9">recently have shared details</a> on what we have been doing so far. Please stay tuned for full disclosure.</p><h3><strong>About Containous Inc.</strong></h3><p>Containous is the company that supports the development of Traefik. We provide professional services to ensure businesses get the most out of the solution.</p><p>With this new product, Containous continues to innovate and define new ways to access microservice platforms, pushing the limits of automation and scalability.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83b78d09efeb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/containous/introducing-traefik-enterprise-edition-83b78d09efeb">Introducing Traefik Enterprise Edition</a> was originally published in <a href="https://medium.com/containous">containous</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Traefik 1.6 — Get Our Latest tetedemoine!]]></title>
            <link>https://medium.com/containous/traefik-1-6-get-our-latest-tetedemoine-1859164bf521?source=rss-12234ecbea0------2</link>
            <guid isPermaLink="false">https://medium.com/p/1859164bf521</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[traefik]]></category>
            <dc:creator><![CDATA[Emile Vauge]]></dc:creator>
            <pubDate>Mon, 07 May 2018 09:29:46 GMT</pubDate>
            <atom:updated>2018-05-07T16:29:44.571Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FA-ZxO_2HjFO9sJpBE1SEw.png" /><figcaption><a href="https://en.wikipedia.org/wiki/T%C3%AAte_de_Moine">Monk’s head</a></figcaption></figure><p>After 3 months of development, we are thrilled to announce the fresh new release of Traefik: <em>1.6</em>, codename “<em>tetedemoine”</em>.</p><p>We merged 168 pull requests from more than 43 contributors! A huge thanks goes out to each of you who helped on this new version 😘.</p><p>The full changelog can be found <a href="https://github.com/containous/traefik/releases/tag/v1.6.0">here</a> but here are some new features we want to highlight:</p><h3>Let’s Encrypt Wildcard Certificates</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*eje9a_eD79KOl2HazUY-UQ.png" /></figure><p>This was a long-awaited feature; we are proud to announce that we officially support Let’s Encrypt wildcard certificates generation, thanks to <a href="https://github.com/nmengin">Nicolas Mengin</a> (and thanks to <a href="https://github.com/xenolf">xenolf</a> to the initial ACMEv2 support in <a href="https://github.com/xenolf/lego">lego</a>). This greatly simplifies certificate management as it avoids generating multiple sub-domains certificates. Now, it’s possible to generate root domain certificates, which will work for every sub-domain.</p><p>Note: ACME wildcard certificates can only be generated thanks to a DNS-01 challenge:</p><pre>[acme]<br># ...<br>[[acme.domains]]<br>  main = &quot;*.local1.com&quot;<br>  sans = [&quot;local1.com&quot;]<br>[[acme.domains]]<br>  main = &quot;*.local2.com&quot;<br># ...</pre><p>No more <a href="https://letsencrypt.org/docs/rate-limits/">Let’s Encrypt rate limits</a> :)</p><h3>Open Tracing &amp; Zipkin support</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*nGPImlOjmAebUHNjugGXGQ.png" /></figure><p>In microservice architectures, being able to reconstruct the elaborate journeys that transactions take as they propagate across a distributed system has become a minimum requirement for effective monitoring.</p><blockquote>OpenTracing allows developers of application code, OSS packages, and OSS services to instrument their own code without binding to any particular tracing vendor.</blockquote><p>We received a wonderful gift from <a href="https://github.com/tcolgate">Tristan Colgate-McFarlane</a> (with the help of <a href="https://github.com/containous/traefik/pull/2587">Michaël Matur</a>) who implemented Open Tracing support, right into Traefik. Have a look at the <a href="https://docs.traefik.io/v1.6/configuration/tracing/">documentation</a> to get more details.</p><h3>New Web UI</h3><p><a href="https://github.com/jkuri">Jan Kuri</a> &amp; <a href="https://github.com/ldez">Ludovic Fernandez</a> revamped our web UI, and we love how shiny it is. Amazing job!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Vvq2ItrZ3q0h8VwDMO8wQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*arWDMTkIqSnYozUf4wLOrg.png" /></figure><h3>TLS Certificates in Kubernetes Secrets</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*C4OGmhd9DZajPhrOp1CRCg.png" /></figure><p>Another awaited feature, <a href="https://github.com/gopenguin">gopenguin</a> added Kubernetes Secrets support for fetching TLS certificates. This enables Traefik to read the Kubernetes secret defined in an ingress resource <a href="https://docs.traefik.io/v1.6/user-guide/kubernetes/#add-a-tls-certificate-to-the-ingress">via the </a><a href="https://docs.traefik.io/v1.6/user-guide/kubernetes/#add-a-tls-certificate-to-the-ingress">tls property</a>:</p><pre>apiVersion: extensions/v1beta1<br>kind: Ingress<br>metadata:<br>  name: traefik-web-ui<br>  namespace: kube-system<br>  annotations:<br>    kubernetes.io/ingress.class: traefik<br>spec:<br>  rules:<br>  - host: traefik-ui.minikube<br>    http:<br>      paths:<br>      - backend:<br>          serviceName: traefik-web-ui<br>          servicePort: 80<br>  tls:<br>   - secretName: traefik-ui-tls-cert</pre><h3>Access Logs Filtering</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*m5kMXf3djJecXVy0i7LR1Q.png" /></figure><p>With the <a href="https://en.wikipedia.org/wiki/General_Data_Protection_Regulation">GDPR</a> becoming real in EU, logging and storage of (potentially) personally identifiable information now need to be reduced in many organizations.</p><p>After a <a href="https://github.com/containous/traefik/issues/2875">public proposal</a>, <a href="https://github.com/containous/traefik/pull/2587">Michaël Matur</a> implemented a way to filter the content of access logs based on simple rules. Your can now keep, dropor redactfields and headers from your access logs. Take a look at <a href="https://docs.traefik.io/v1.6/configuration/logs/#access-logs">our documentation</a> to get a deeper insight.</p><h3>Labels Homogenization</h3><p>Probably one of the biggest refactoring of all time on Traefik, <a href="https://github.com/ldez">Ludovic Fernandez</a> changed the way we manage labels internally, in order to homogenize labels on all providers. We now support all labels on all providers, no more specific code on this part 🎉</p><p>This will make it a lot easier to maintain, and we will be able to ship new features faster on all providers.</p><p>But that’s not all, check the whole <a href="https://github.com/containous/traefik/releases/tag/v1.6.0">changelog</a> to get an idea of the awesome work that has been done on this release. Lots of bugs have been fixed and we also have been working on background refactoring tasks that will help us improving Traefik in future releases.</p><p>Grab the latest binary for Linux, Windows, Mac on Github or get the official Docker image!</p><pre>docker pull traefik:v1.6.0 (or 1.6.0, v1.6, 1.6, tetedemoine)<br>docker pull traefik:v1.6.0-alpine (or 1.6.0-alpine, v1.6-alpine, 1.6-alpine, tetedemoine-alpine)</pre><p>The <em>versioned</em> documentation can be found on <a href="https://docs.traefik.io/">https://docs.traefik.io</a>.</p><p><strong>We are hiring developers and evangelists, try to solve our puzzle:</strong><a href="https://containo.us/#jobs"><strong>containo.us/#jobs</strong></a><strong> !</strong></p><p>Traefik is still growing fast, we almost passed <strong>15k stars</strong> on Github and <strong>90M downloads</strong>!</p><p>We would love to hear your feedback on this new release. Join us on <a href="https://github.com/containous/traefik">GitHub</a>, <a href="https://twitter.com/traefikproxy">Twitter</a> or <a href="http://slack.traefik.io/">Slack</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1859164bf521" width="1" height="1" alt=""><hr><p><a href="https://medium.com/containous/traefik-1-6-get-our-latest-tetedemoine-1859164bf521">Traefik 1.6 — Get Our Latest tetedemoine!</a> was originally published in <a href="https://medium.com/containous">containous</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Traefik — Commercial Support Is Coming!]]></title>
            <link>https://medium.com/containous/commercial-support-is-coming-for-traefik-a28a2caf1e91?source=rss-12234ecbea0------2</link>
            <guid isPermaLink="false">https://medium.com/p/a28a2caf1e91</guid>
            <category><![CDATA[announcements]]></category>
            <category><![CDATA[containous]]></category>
            <category><![CDATA[traefik]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[reverse-proxy]]></category>
            <dc:creator><![CDATA[Emile Vauge]]></dc:creator>
            <pubDate>Tue, 10 Apr 2018 09:58:23 GMT</pubDate>
            <atom:updated>2018-04-27T08:51:56.809Z</atom:updated>
            <content:encoded><![CDATA[<h4>Season 1, Episode 1</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KnlNoi0R9mJTTVLN-O6iog.jpeg" /></figure><p>At Containous, we’re excited to share the news — Starting today, we’ll provide commercial support for Træfik.</p><p>We’re thrilled because beyond the mere satisfaction of helping you, it means that Træfik has reached yet another level of maturity. Not only is Træfik this easy-to-set-up full-fledged incredible reverse proxy; it is now a project we deem stable enough (roadmap-wise) to assure our future customers that we’ll be able to back them up when they most need it.</p><p><strong>Making sure that every professional can rely on Træfik for their infrastructure is our top priority.</strong></p><p>We’ve had lots of discussions about the possible plans we could provide to companies. The SLAs, the price, the ticket system … so many parameters that have stirred the fire of passion in our geek-crowded office.</p><p>We have finally settled on a plan that will fit the needs of most companies that already trust Træfik (or are about to), and that need this supplementary insurance — Yes, our team of experts will now be available to make sure <em>every</em> edge case of your specific set-up is handled correctly.</p><p>So, what does this standard plan consist of?</p><ul><li>We will support each major version of Træfik (we use <a href="https://semver.org/">semantic versioning</a>) for a whole year after the next one is released. For example, once 2.0 is released, we will continue to support 1.n for one year (n being the latest minor version in that branch).</li><li><em>During</em> a major release cycle, in addition to supporting the current version, we will support the previous one. For example, once 1.8 is released, we will continue to support 1.7 (but will stop supporting 1.6) until 1.9 or 2.0 is released.</li><li>We will start working on any question you have within 2 hours of you contacting us (business hours, CET).</li></ul><p>Now we see your question coming, “What happens to the community support?”</p><p>Our answer cannot be simpler — nothing changes.</p><blockquote>Open source drives Træfik, and we will keep doing our best to make Træfik one of the most successful open-source projects ever.</blockquote><p><strong>Have we talked about the price yet?</strong></p><p>Træfik‘s success is propelled by its simplicity. Simplicity means that it reaches a broad audience, from the most straightforward infrastructure to intricate clusters with multiple layers of orchestration.</p><p>Our goal with the standard plan is to be able to provide support at an affordable price so that everyone can benefit from it.</p><p>For this reason, we concurred on a price that will allow a wide range of companies to subscribe to the standard support plan (without sacrificing other investments in their program).</p><p>Starting at €1,000 per instance of Træfik , you’ll benefit from our services for a whole year.</p><p>The standard plan can go as far as five supported instances of Træfik running on your infrastructure.</p><p><strong>Need more support?</strong></p><p>If your business requires a customized support plan, you can contact us to discuss further how we can help.</p><p>Oh … by the way … you’ll find the form to request support on <a href="https://containo.us/services#commercial-support">our new website</a>!</p><figure><a href="https://containo.us/services#commercial-support"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AxQdygZStB1waHchOdOl_A.jpeg" /></a></figure><p>Happy Træfik!</p><p>Containous is the company that helps Træfik be the successful open-source project it is.</p><p>Follow <a href="https://twitter.com/containous">Containous</a> &amp; <a href="https://twitter.com/traefikproxy">Træfik</a> on Twitter.</p><p><a href="http://containo.us/">Visit our website.</a></p><p>Share your opinion in the comments section.</p><p>And don’t forget, you’ll always be welcome on the <a href="http://slack.traefik.io/">Træfik Slack workspace</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a28a2caf1e91" width="1" height="1" alt=""><hr><p><a href="https://medium.com/containous/commercial-support-is-coming-for-traefik-a28a2caf1e91">Traefik — Commercial Support Is Coming!</a> was originally published in <a href="https://medium.com/containous">containous</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Traefik 1.5 — Cancoillotte Is Here!]]></title>
            <link>https://medium.com/containous/traefik-1-5-cancoillotte-is-here-7bd6713ae135?source=rss-12234ecbea0------2</link>
            <guid isPermaLink="false">https://medium.com/p/7bd6713ae135</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[lets-encrypt]]></category>
            <category><![CDATA[traefik]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Emile Vauge]]></dc:creator>
            <pubDate>Wed, 24 Jan 2018 08:36:44 GMT</pubDate>
            <atom:updated>2018-01-24T08:39:00.398Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bLR_qbi3qufT5w0EWxVGrg.png" /><figcaption>Try to <a href="https://www.youtube.com/watch?v=kOnUeb1Ck-8">pronounce it right</a> ;)</figcaption></figure><p>After 3 months of development, we are thrilled to announce the fresh new release of Traefik: <em>1.5</em>, codename <a href="https://en.wikipedia.org/wiki/Cancoillotte"><em>cancoillotte</em></a>.</p><p>We merged 175 pull requests from more than 67 contributors ! Huge thanks goes to all of you who helped on this new version 😘.</p><p>The full changelog can be found <a href="https://github.com/containous/traefik/releases/tag/v1.5.0">here</a> but here are some new features we want to highlight:</p><h3>Let’s Encrypt HTTP Challenge</h3><p>On January the 9th, a little surprise appeared on our Twitter timeline:</p><p><a href="https://community.letsencrypt.org/t/2018-01-09-issue-with-tls-sni-01-and-shared-hosting-infrastructure/49996">2018.01.09 Issue with TLS-SNI-01 and Shared Hosting Infrastructure</a></p><p>And then:</p><p><a href="https://community.letsencrypt.org/t/2018-01-11-update-regarding-acme-tls-sni-and-shared-hosting-infrastructure/50188">2018.01.11 Update Regarding ACME TLS-SNI and Shared Hosting Infrastructure</a></p><p><strong>TL;DR</strong>: Let’s Encrypt permanently disabled TLS-SNI-0x challenge due to a vulnerability.</p><p>And yes, Traefik was using TLS-SNI-01 challenge by default. Ouch…</p><p>Even though we were at the end of a release cycle (<em>1.5.0-rc4</em> was already out), we decided to push a new release candidate in emergency to add HTTP-01 challenge support. This fix was big enough to end in the new <em>1.5</em> and not as a bug fix on <em>1.4</em> branch. Users will need to <a href="https://docs.traefik.io/configuration/acme/#acmehttpchallenge">enable it</a> with the new acme.httpChallenge section.</p><h3>Stats Collection</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/1*NDPH-CA1vsUbuL2ZgbBnFw.jpeg" /></figure><p>Few months ago, we created <a href="https://github.com/containous/traefik/issues/2369">a proposal</a> in which we came up with the idea of collecting stats from running Traefik instances:</p><blockquote>As you may know, the Traefik core development team is quite small and as with a lot of open source projects, we lack time and resources. As a consequence, we have to carefully choose which tasks and features need our attention. As a result, we usually invest our time on features needed or requested by most of the community. In order to efficiently do this, we have to know how our community uses Traefik.</blockquote><p>As this is a super sensitive topic, we preferred to open a public debate, and build a transparent and trusted solution with the community. We are excited to say that we quickly reached a consensus, and <a href="https://github.com/ldez">Ludovic Fernandez</a> successfully implemented a safe configuration export mechanism.</p><p><strong>We chose to make it opt-in</strong>, which means that no data will be sent without enabling this feature. If enabled, <strong>only anonymous configuration</strong> options will be sent to a collecting server.</p><p>We really hope that all of our efforts will pay off, and that you will <strong>help us improve Traefik enabling this feature</strong> in your infrastructure:</p><pre>sendAnonymousUsage = true</pre><p><em>We invite you to read </em><a href="https://github.com/containous/traefik/issues/2369"><em>the constructive discussion</em></a><em> that led to this new feature and </em><a href="https://docs.traefik.io/basics/#collected-data"><em>the documentation</em></a><em> to get more details. Many thanks to the community for its positive feedback!</em></p><h3>Dynamic TLS Certificates</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/523/1*5mQKqaUGXJkce29rksyZKg.png" /></figure><p><a href="https://github.com/nmengin">Nicolas Mengin</a> did a great job at making TLS certificates management dynamic. You can now add or remove TLS certificates while Traefik is started! In addition to backends and frontends, there is now a dedicated tls section in the dynamic configuration. Let’s declare two new certificates using the <a href="https://docs.traefik.io/v1.5/configuration/backends/file/">file provider</a>, you can now add a new tls section in your TOML:</p><pre>[frontends]<br>...<br>[backends]<br>...</pre><pre># HTTPS certificates<br>[[tls]]<br>  entryPoints = [&quot;https&quot;]<br>  [tls.certificate]<br>    certFile = &quot;path/to/my.cert&quot;<br>    keyFile = &quot;path/to/my.key&quot;</pre><pre>[[tls]]<br>  entryPoints = [&quot;https&quot;]<br>  [tls.certificate]<br>  certFile = &quot;path/to/my/other.cert&quot;<br>  keyFile = &quot;path/to/my/other.key&quot;</pre><p>Each change of this file will make Traefik reload its TLS certificates. You can also split your configuration into multiple files if you prefer.</p><h3>Rate Limiting</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*4EVuBv-yYaTmVj2sAbyZlw.png" /></figure><p>We received a wonderful gift from <a href="https://github.com/bparli">Ben Parli</a> who added rate limiting by frontend. You can even add multiple sets of rates to each frontend. Here is an example taken from <a href="https://docs.traefik.io/configuration/commons/#rate-limiting">the documentation</a>:</p><pre>[frontends]<br>    [frontends.frontend1]<br>    entrypoints = [&quot;http&quot;]<br>    backend = &quot;backend1&quot;<br>        [frontends.frontend1.routes.test_1]<br>        rule = &quot;Path:/&quot;<br>    [frontends.frontend1.ratelimit]<br>    extractorfunc = &quot;client.ip&quot;<br>        [frontends.frontend1.ratelimit.rateset.rateset1]<br>        period = &quot;10s&quot;<br>        average = 100<br>        burst = 200<br>        [frontends.frontend1.ratelimit.rateset.rateset2]<br>        period = &quot;3s&quot;<br>        average = 5<br>        burst = 10</pre><blockquote>In the above example, frontend1 is configured to limit requests by the client’s ip address. An average of 5 requests every 3 seconds is allowed and an average of 100 requests every 10 seconds. These can “burst” up to 10 and 200 in each period respectively.</blockquote><h3>Azure Service Fabric Support</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*Blppz5asuLmYdMREWHolCg.png" /></figure><p><a href="https://github.com/lawrencegripper">Lawrence Gripper</a> and <a href="https://github.com/jjcollinge">Joni Collinge</a> from Microsoft made a great contribution (with the help of <a href="https://github.com/ldez">Ludovic Fernandez</a>) adding <a href="https://azure.microsoft.com/en-us/services/service-fabric/">Azure Service Fabric</a> support to Traefik.</p><blockquote>Azure Service Fabric is a distributed systems platform that makes it easy to package, deploy, and manage scalable and reliable microservices and containers.</blockquote><p>This new provider uses labels to configure how services are exposed through Traefik using the services ServiceManifest.xml file.</p><p>Have a look at <a href="http://docs.traefik.io/configuration/backends/servicefabric/">the documentation</a>, we will give more update on this soon!</p><h3>In A Nutshell</h3><p><a href="https://github.com/dtomcej">Daniel Tomcej</a> added Kubernetes annotations and Docker labels for security headers, <a href="https://github.com/nmengin">Nicolas Mengin</a> added support to etcd v3, our great <a href="https://github.com/SantoDE">Manuel Zapf</a> implemented the redirection to another entryPoint per frontend.<br>Thanks to <a href="https://github.com/adityacs">Aditya C S</a>, Traefik can now export its metrics to InfluxDB. <a href="https://github.com/mmatur">Michael Matur</a> and <a href="https://github.com/ldez">Ludovic Fernandez</a> did a great job adding multi-versioning to our documentation (from <a href="https://docs.traefik.io/v1.0">https://docs.traefik.io/v1.0</a> to <a href="https://docs.traefik.io/v1.5">http://docs.traefik.io/v1.5</a>). <a href="https://github.com/juliens">Julien Salleyron</a> refactored the web provider into API/Dashboard, ping, metric and Rest Provider.</p><p>But that’s not all, check the whole <a href="https://github.com/containous/traefik/releases/tag/v1.5.0">changelog</a> to get an idea of the awesome work that has been done on this release. Lots of bugs have been fixed and we also have been working on background refactoring tasks that will help us improving Traefik in future releases.</p><p>Grab the latest binary for Linux, Windows, Mac on Github or get the official Docker image!</p><pre>docker pull traefik:v1.5.0 (or 1.5.0, v1.5, 1.5, cancoillotte)<br>docker pull traefik:v1.5.0-alpine (or 1.5.0-alpine, v1.5-alpine, 1.5-alpine, cancoillotte-alpine)</pre><p>The <em>versioned</em> documentation can be found on <a href="https://docs.traefik.io/">https://docs.traefik.io</a>.</p><p><strong>We are hiring developers and evangelists, try to solve our puzzle: </strong><a href="https://containo.us/#jobs"><strong>containo.us/#jobs</strong></a><strong> !</strong></p><p>Traefik is still growing fast, we just passed <strong>12k stars</strong> on Github and <strong>42M downloads</strong>!</p><p>We would love to hear your feedback on this new release. Join us on <a href="https://github.com/containous/traefik">GitHub</a>, <a href="https://twitter.com/traefikproxy">Twitter</a> or <a href="http://slack.traefik.io/">Slack</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7bd6713ae135" width="1" height="1" alt=""><hr><p><a href="https://medium.com/containous/traefik-1-5-cancoillotte-is-here-7bd6713ae135">Traefik 1.5 — Cancoillotte Is Here!</a> was originally published in <a href="https://medium.com/containous">containous</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Solving containous/jobs]]></title>
            <link>https://medium.com/containous/solving-containous-jobs-b4a5cae04f3?source=rss-12234ecbea0------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4a5cae04f3</guid>
            <category><![CDATA[puzzle]]></category>
            <category><![CDATA[containous]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[traefik]]></category>
            <dc:creator><![CDATA[Emile Vauge]]></dc:creator>
            <pubDate>Tue, 14 Nov 2017 08:04:51 GMT</pubDate>
            <atom:updated>2017-11-14T10:58:46.462Z</atom:updated>
            <content:encoded><![CDATA[<p>Last year, we had this idea to create a little puzzle to hire new engineers on <a href="https://traefik.io/">Traefik</a>.</p><h3>Træfik on Twitter</h3><p>⚡️We are hiring⚡️ $ docker run containous/jobs</p><p>As we are deeply linked to Docker on this project, we thought it would be great to focus on technical challenges around containers. So we pushed a Docker image:</p><pre><strong>$ docker run containous/jobs<br>Do you like puzzles ?</strong></pre><p>Few people informed us that our image must have an issue as it was only printing <em>Do you like puzzles ?</em>. Yup. That was the whole point. Something was indeed hidden here, and you had to find it 😉</p><p>Let’s jump into it!</p><p>First of all, how is made containous/job ?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HPihjUpRf1SpugElgwx8KQ.png" /></figure><p>Not really helpful… But there seems to be two files copied during the build process. docker inspect containous/jobs shows that /default is the entrypoint. Another file should be hidden there 😃</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BnvkKfADeRf7_D8TuvA0lQ.png" /></figure><p>If we export the container file system using <a href="https://docs.docker.com/engine/reference/commandline/export/">docker export</a>, we see that there is our /default binary, and there is also, surprisingly, another binary: /secret. Wow ! Let’s test something…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tpz8H8xIszVU7M6xEhh3JQ.png" /></figure><blockquote><em>Lineception… Kill me… Just kill me…</em></blockquote><p>OK, so our container is not exiting anymore, until we press enter and then we get <em>Game over :’(</em>. Hum, not that easy 🤔</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LIXSaSvjiziempTBY5t-0w.png" /></figure><blockquote><em>Kill me… Just kill me…</em></blockquote><p>If we try to kill the container, it exits, but this time, without printing <em>Game over :’(. </em>Ha ! Let’s try with another kill signals then ! After few tries, you will end up using SIGABRT:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6-iZXOTAPWoILnzZzrKLGg.png" /></figure><p>A wonderful stack trace is now on the screen. We can see that this binary has been created using go 1.7, and that the repository of the code is bitbucket.org/containous/jobs. Wait a minute… What ?</p><p><strong>WE JUST FOUND WHERE IS HOSTED THE SOURCE CODE !!!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pOXypDRYDq0imB4KGX1UcQ.png" /></figure><p>Damn private repository…</p><p>Let’s start from the beginning. If we look closely at each step, we used every piece of clue given by our Docker image. Except one:</p><blockquote><em>Lineception…</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*fsIwSbTlWXNgXg5ywotWuQ.jpeg" /></figure><p><strong>Lineception = line + inception</strong></p><p>Which line of our code is called when calling kill with SIGABRT?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3DiXA-F3W4pJlGU9lT4yAg.png" /></figure><pre>bitbucket.org/containous/jobs/cmd/secret/secret.go:15</pre><p>And now:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-neJ3HiFsCPHuXClMieyuA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*4OeQBkMmsn5oG7rBToiAog.gif" /></figure><p>And that’s it!</p><p>It seems that the final part was a bit too complex as a lot a people found alternatives solutions. Many of you discovered a base 64 encoded string right into the binary:</p><pre>V2VsbCBkb25lIQ0KV2Ugd291bGQgbG92ZSB0byBrbm93IG1vcmUgYWJvdXQgeW91Lg0KUGxlYXNlIHNlbmQgdXMgYSBtYWlsIGF0IGpvYnMgYXQgY29udGFpbm8udXMgYW5kIHRlbGwgdXMgaG93IHlvdSBzb2x2ZWQgdGhpcyBwdXp6bGUgYW5kIHdoeSB5b3Ugd2FudCB0byB3b3JrIGF0IENvbnRhaW5vdXMgOikNCig1MCB3b3JkcyBtYXgpDQo=</pre><p>And yes, once decoded, you get straight away:</p><pre>Well done!<br>We would love to know more about you.<br>...</pre><p>In fact, very few people found the right solution using the line number. I would like to congratulate <a href="https://medium.com/u/f9295502fb9b">Cédric Nisio</a> who was the first who solved this puzzle. Well done 👏👏👏</p><p>We really loved to read your feedback and answers on this little game and we think it’s now time to try something new 😉</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/922/1*UqnM7Zb2Et3nfGNmzV9QNQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4a5cae04f3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/containous/solving-containous-jobs-b4a5cae04f3">Solving containous/jobs</a> was originally published in <a href="https://medium.com/containous">containous</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Traefik 1.4 — Roquefort Is Here, And It’s Huge!]]></title>
            <link>https://medium.com/containous/traefik-1-4-roquefort-is-here-and-its-huge-c26654aba80f?source=rss-12234ecbea0------2</link>
            <guid isPermaLink="false">https://medium.com/p/c26654aba80f</guid>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[traefik]]></category>
            <dc:creator><![CDATA[Emile Vauge]]></dc:creator>
            <pubDate>Tue, 17 Oct 2017 06:21:01 GMT</pubDate>
            <atom:updated>2017-10-17T06:21:01.176Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2NS3OACEy6JsCzcK8EVwDw.png" /><figcaption>Rock Fort…</figcaption></figure><p>After 4 months of intense development, we are proud to announce the fresh new release of Traefik: <em>1.4</em>, codename <a href="https://en.wikipedia.org/wiki/Roquefort"><em>roquefort</em></a><em>.</em></p><p>This release is quite big: we merged <a href="https://github.com/containous/traefik/pulls?utf8=%E2%9C%93&amp;q=is%3Apr%20milestone%3A1.4%20is%3Amerged">250</a> pull requests from more than 60 contributors ! Huge thanks goes to all of you who helped on this new version 😘.</p><p>The full changelog can be found <a href="https://github.com/containous/traefik/releases/tag/v1.4.0">here</a> but here are some new features we want to highlight:</p><h3>Custom Headers &amp; Security</h3><p>Our awesome <a href="https://github.com/dtomcej">Daniel Tomcej</a> did some hard work on headers. <a href="http://docs.traefik.io/basics/#custom-headers">We now have a way</a> to customize headers:</p><blockquote>Custom headers can be configured through the frontends, to add headers to either requests or responses that match the frontend’s rules. This allows for setting headers such as X-Script-Name to be added to the request, or custom headers to be added to the response.</blockquote><p>If that was not enough, Daniel <a href="http://docs.traefik.io/basics/#security-headers">added security options</a> on headers:</p><blockquote>Security related headers (HSTS headers, SSL redirection, Browser XSS filter, etc) can be added and configured per frontend in a similar manner to the custom headers above. This functionality allows for some easy security features to quickly be set.</blockquote><h3>Multi arch</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4HiqzRbB0Fkus-5qfM4juA.jpeg" /></figure><p>Thanks to <a href="https://github.com/ldez">Ludovic Fernandez</a>, <a href="https://github.com/docker-library/official-images/blob/master/library/traefik">we now provide</a> the official Docker image on multiple architectures: <em>amd64</em>, <em>arm64v8</em>, <em>arm32v6</em>. The best part is that as of mid-September, Docker supports <a href="https://blog.docker.com/2017/09/docker-official-images-now-multi-platform">transparent multi-arch on official images</a>. This allows to use docker run traefik transparently either on a <em>amd64 </em>or a<em> arm64v8 </em>Docker daemon. We plan to add a Windows based official image in the future.</p><h3>Authentication Forward</h3><p>As a first step to <a href="https://github.com/containous/traefik/issues/593">a generic authentication mechanism</a>, <a href="https://github.com/drampelt">Daniel Rampelt</a> followed by <a href="https://github.com/ldez">Ludovic Fernandez</a>, added a way to forward authentication to a delegate server. Have a look at <a href="https://github.com/containous/traefik/pull/1972">both</a> <a href="https://github.com/containous/traefik/pull/2132">PRs</a> to get more details on this.</p><h3>Proxy Protocol</h3><p>Traefik is often used behind another load-balancer like an <a href="https://aws.amazon.com/elasticloadbalancing">ELB</a>. In this case, Traefik now supports <a href="https://www.haproxy.org/download/1.8/doc/proxy-protocol.txt">Proxy Protocol</a>, that allows to keep client information between the chain of proxies. Have a look at <a href="http://docs.traefik.io/configuration/entrypoints/#proxyprotocol">the documentation</a> to learn how to enable and configure safely this feature.</p><h3>Custom Error Pages</h3><p><a href="https://github.com/bparli">Ben Parli</a> did some great job on adding custom error pages support into Traefik. But instead of rendering html pages, we decided to delegate this task to a backend server. <a href="http://docs.traefik.io/configuration/commons/#custom-error-pages">You can now configure Traefik</a> to get error pages from another server, using this syntax:</p><pre>[frontends]<br>  [frontends.website]<br>  backend = &quot;website&quot;<br>  [frontends.website.errors]<br>    [frontends.website.errors.network]<br>    status = [&quot;500-599&quot;]<br>    backend = &quot;error&quot;<br>    query = &quot;/{status}.html&quot;<br>  [frontends.website.routes.website]<br>  rule = &quot;Host: website.mydomain.com&quot;<br><br>[backends]<br>  [backends.website]<br>    [backends.website.servers.website]<br>    url = &quot;<a href="https://1.2.3.4/">https://1.2.3.4</a>&quot;<br>  [backends.error]<br>    [backends.error.servers.error]<br>    url = &quot;<a href="http://2.3.4.5/">http://2.3.4.5</a>&quot;</pre><p>In this example, if you hit a 502 error, Traefik will ask to the backend server <a href="http://2.3.4.5/">http://2.3.4.5</a> for the page 502.html.</p><h3>Datadog, Statd metrics export</h3><p><a href="https://github.com/aantono">Alex Antonov</a> <a href="http://docs.traefik.io/configuration/backends/web/#metrics">completed the existing Prometheus metrics export</a> with two famous monitoring services: Datadog and Statd. This allows to easily export internal Traefik metrics to monitoring systems and get <a href="https://grafana.com/dashboards/2240">Grafana dashboards</a> of your running instances.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mnukQ34_0YZXSzV5KiASoQ.png" /></figure><h3>In A Nutshell</h3><p><a href="https://github.com/juliens">Julien Salleyron</a> added <a href="https://grpc.io/">GRPC</a> support and made a <a href="http://docs.traefik.io/user-guide/grpc/">great user guide</a> on this.<br>We now allow to customize cookie names thanks to <a href="https://github.com/ldez">Ludovic Fernandez</a>, see the documentation <a href="http://docs.traefik.io/basics/#sticky-sessions">here</a>.<br><a href="https://github.com/drewwells">Drew Wells</a> added the option passTLSCertto forward TLS Client certificates to the backend.<br>The documentation website <a href="https://docs.traefik.io/">https://docs.traefik.io</a> has been revamped by <a href="https://github.com/ldez">Ludovic Fernandez</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SsQ2Et_pazAuSUmU1axxCA.png" /></figure><p>But that’s not all, check the <a href="https://github.com/containous/traefik/releases/tag/v1.4.0">whole changelog</a> to get an idea of the awesome work that has been done on this release. Lots of bugs have been fixed and we also have been working on <a href="https://github.com/containous/gallienii">creating</a> <a href="https://github.com/containous/lobicornis">awesome</a> <a href="https://github.com/containous/bibikoffi">bots</a> <a href="https://github.com/containous/aloba">that</a> <a href="https://github.com/traefiker">do</a> great things for us.</p><p>Grab the latest binary for Linux, Windows, Mac on <a href="https://github.com/containous/traefik/releases/tag/v1.2.0">Github</a> or get the <a href="https://hub.docker.com/_/traefik/">official Docker image</a>!</p><pre>docker pull traefik:v1.4.0 (or 1.4.0, v1.4, 1.4, roquefort)<br>docker pull traefik:v1.4.0-alpine (or 1.4.0-alpine, v1.4-alpine, 1.4-alpine, roquefort-alpine)</pre><p>The documentation can be found on <a href="https://docs.traefik.io/">https://docs.traefik.io</a>.</p><p>We are thrilled to welcome <a href="https://github.com/mmatur">Michael Matur</a> who joined <a href="https://containo.us/">Containous</a> and <a href="https://github.com/marco-jantke">Marco Jantke</a> who joined the maintainers team 👋 ! <strong>We are hiring developers and evangelists: </strong><a href="https://containo.us/#jobs"><strong>containo.us/#jobs</strong></a><strong> !</strong></p><p>Traefik is still growing fast, we just passed <a href="https://github.com/containous/traefik/stargazers">10k stars</a> on Github and 22M downloads!</p><p>We would love to hear your feedback on this new release. Join us on <a href="https://github.com/containous/traefik">GitHub</a>, <a href="https://twitter.com/traefikproxy">Twitter</a> or <a href="https://traefik.herokuapp.com/">Slack</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c26654aba80f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/containous/traefik-1-4-roquefort-is-here-and-its-huge-c26654aba80f">Traefik 1.4 — Roquefort Is Here, And It’s Huge!</a> was originally published in <a href="https://medium.com/containous">containous</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Traefik 1.3 — Get Some More Raclette !]]></title>
            <link>https://medium.com/containous/traefik-1-3-get-some-more-raclette-1046664d862b?source=rss-12234ecbea0------2</link>
            <guid isPermaLink="false">https://medium.com/p/1046664d862b</guid>
            <category><![CDATA[traefik]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[golang]]></category>
            <dc:creator><![CDATA[Emile Vauge]]></dc:creator>
            <pubDate>Thu, 01 Jun 2017 06:07:08 GMT</pubDate>
            <atom:updated>2017-06-01T06:07:08.995Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/611/1*iPjSJPBOsZGGmuijQSQOrw.png" /></figure><p>We released Traefik <em>1.2</em> only <a href="https://blog.containo.us/traefik-1-2-morbier-is-out-8bc304a66ef3">two months ago</a>, and we are proud to announce that the fresh new Traefik <em>1.3</em>, codename <a href="https://en.wikipedia.org/wiki/Raclette"><em>raclette</em></a> is out!</p><p>As Traefik is getting bigger and bigger, we decided to accelerate things and to release more often. From a 4 months release cycle, you will now have to wait only 2 months between each release.</p><p>The full changelog can be found <a href="https://github.com/containous/traefik/releases/tag/v1.3.0">here</a> but here are some new features we want to highlight:</p><h3>Multiple Rules by Container</h3><p>Thanks to <a href="https://github.com/benoitf">Florent Benoit</a>, Traefik can now manage multiple rules by container, <a href="https://github.com/containous/traefik/pull/1257">introducing service labels</a>. You can now easily forward multiple ports from a same container :) Here are all available labels:</p><pre>traefik.&lt;service-name&gt;.port<br>traefik.&lt;service-name&gt;.weight<br>traefik.&lt;service-name&gt;.protocol<br>traefik.&lt;service-name&gt;.frontend.backend<br>traefik.&lt;service-name&gt;.frontend.entryPoints<br>traefik.&lt;service-name&gt;.frontend.rule<br>traefik.&lt;service-name&gt;.frontend.passHostHeader<br>traefik.&lt;service-name&gt;.frontend.priority<br>traefik.&lt;service-name&gt;.frontend.rule</pre><h3>Amazon DynamoDB support</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*PDXSGjGFEmGlD3F9fFnlEA.png" /></figure><p><a href="https://github.com/tskinn">Tskinn</a> made a great job on <a href="https://github.com/containous/traefik/pull/1158">integrating</a> Traefik with <a href="https://aws.amazon.com/fr/dynamodb/">Amazon DynamoDB</a>, a flexible NoSQL database service. You can now push your configuration (frontends and backends) into this database and Traefik will watch any changes dynamically.</p><h3>Basic Authentication per Frontend</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/224/1*LXzqFevT1u6ZvjIPTPg3bA.png" /></figure><p>Another awaited feature, <a href="https://github.com/santode">Manuel Laufenberg</a> added <a href="https://github.com/containous/traefik/pull/1147">basic authentication per frontend</a> configuration (it was only globally configurable initially). Currently, Docker and Rancher backends are supported, more will be added in the future!</p><h3>Dashboard Filter</h3><p><a href="https://github.com/ldez">Ludovic Fernandez</a> added <a href="https://github.com/containous/traefik/pull/1437">a nice little feature</a> in the webui: you now can filter frontends and backends. When you have a big configuration with many routes, it’s really handy to be able to quickly find what you want.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xlVix6Jo7eJvcNNx0YKIeg.png" /></figure><p>But that’s not all, check the <a href="https://github.com/containous/traefik/releases/tag/v1.3.0">whole changelog</a> to get an idea of the awesome work that has been done on this release. Lots of bugs have been fixed and we have begun a strong background work on our CI infrastructure and project quality in general.</p><p>Grab the latest binary for Linux, Windows, Mac on <a href="https://github.com/containous/traefik/releases/tag/v1.2.0">Github</a> or get the <a href="https://hub.docker.com/_/traefik/">official Docker image</a>!</p><pre>docker pull traefik:v1.3.0 (or 1.3.0, v1.3, 1.3, raclette)<br>docker pull traefik:v1.3.0-alpine (or 1.3.0-alpine, v1.3-alpine, 1.3-alpine, raclette-alpine)</pre><p>The documentation can be found on <a href="https://docs.traefik.io/">https://docs.traefik.io</a>.</p><p>Following our <a href="https://blog.containo.us/containous-raises-1-million-in-seed-round-funding-to-develop-traefik-f8238f47d2c7">$1M seed</a>, 4 new developers joined <a href="https://containo.us/">Containous</a> and are now part of the maintainers team. We are thrilled to welcome <a href="https://github.com/ldez">Ludovic Fernandez</a>, <a href="https://github.com/atbore-phx">Attilio Borello</a>, <a href="https://github.com/Juliens">Julien Salleyron</a> and <a href="https://github.com/nmengin">Nicolas Mengin</a> 👋 !</p><p>Traefik is still growing fast, we just passed <a href="https://github.com/containous/traefik/stargazers">8k stars</a> on Github and 7M downloads!</p><p>We would love to hear your feedback on this new release. Join us on <a href="https://github.com/containous/traefik">GitHub</a>, <a href="https://twitter.com/traefikproxy">Twitter</a> or <a href="https://traefik.herokuapp.com/">Slack</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1046664d862b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/containous/traefik-1-3-get-some-more-raclette-1046664d862b">Traefik 1.3 — Get Some More Raclette !</a> was originally published in <a href="https://medium.com/containous">containous</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Traefik 1.2 Morbier is out!]]></title>
            <link>https://medium.com/containous/traefik-1-2-morbier-is-out-8bc304a66ef3?source=rss-12234ecbea0------2</link>
            <guid isPermaLink="false">https://medium.com/p/8bc304a66ef3</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[prometheus]]></category>
            <category><![CDATA[rancher]]></category>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Emile Vauge]]></dc:creator>
            <pubDate>Wed, 22 Mar 2017 07:17:01 GMT</pubDate>
            <atom:updated>2017-03-22T07:17:01.336Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I8--neehI6DYcXYC-PDVJA.png" /></figure><p>After 4 months of hard work, we are proud to announce a new release of Traefik: version <em>1.2.0</em>, codename <a href="https://en.wikipedia.org/wiki/Morbier_cheese"><em>Morbier</em></a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TXP7UKcgxJTWVTSs14B5Zw.png" /></figure><p>The full changelog can be found <a href="https://github.com/containous/traefik/releases/tag/v1.2.0">here</a> but here are some new features we want to highlight:</p><h3>Amazon EC2 Container Service</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*WlPSwlWnO5aOZKKzEmmuTg.png" /></figure><p>Thanks to <a href="https://github.com/lpetre">Luke Petre</a>, Traefik now supports <a href="https://aws.amazon.com/fr/ecs">Amazon EC2 Container Service</a>. This is a great news for AWS fans who need more than an ELB/ALB to manage their inbound traffic.</p><h3>Rancher</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*Zj45ptixryW7q8XjNpnj6Q.png" /></figure><p>Finally, Traefik gets native Rancher support! Thank you <a href="https://github.com/santode">Manuel Laufenberg</a>! It is now a lot simpler to have a specific configuration backend right into Traefik.</p><h3>Prometheus</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*DwY47SdgWoDlpMRJGExAWw.png" /></figure><p>A lot of people were waiting for it, thanks to <a href="https://github.com/enxebre">Alberto Garcial</a>, native Prometheus support is now real :) This allows you to export internal metrics to Prometheus using a simple flag —web.metrics.prometheus. More internal metrics will be added soon!</p><h3>Netflix Eureka</h3><p><a href="https://github.com/Netflix/eureka">Eureka</a> is the service registry taken from the Netflix OSS stack. Traefik now supports Eureka as a configuration backend thanks to <a href="https://github.com/Juliens">Julien Salleyron</a>!</p><h3>Healthchecks</h3><p>Another long awaited feature, healthchecks are here! Again, thanks to <a href="https://github.com/Juliens">Julien Salleyron</a>. A health check can be configured in order to remove a backend from LB rotation as long as it keeps returning HTTP status codes other than 200 OK.</p><p>Grab the latest binary for Linux, Windows, Mac on <a href="https://github.com/containous/traefik/releases/tag/v1.2.0">Github</a> or get the <a href="https://hub.docker.com/_/traefik/">official Docker image</a>!</p><pre>docker pull traefik:v1.2.0<br>docker pull traefik:morbier<br>docker pull traefik:v1.2.0-alpine<br>docker pull traefik:morbier-alpine</pre><p>The documentation can be found on <a href="https://docs.traefik.io/">https://docs.traefik.io</a>.</p><p>In case you missed it, we <a href="https://blog.containo.us/containous-raises-1-million-in-seed-round-funding-to-develop-traefik-f8238f47d2c7">just raised $1M</a> :) You can expect a lot of new features in the coming months, as well as <a href="https://github.com/containous/traefik/issues/1266">background work</a>. Of course, all this will be done involving the community as much as possible.</p><p>Traefik is still growing fast, we just passed <a href="https://github.com/containous/traefik/stargazers">7k stars on Github</a> and 3.5M downloads! The maintainer team gains 2 more maintainers, <a href="https://github.com/trecloux">Thomas Recloux</a> &amp; <a href="https://github.com/timoreimann">Timo Reimann</a> 👋!</p><p>We would love to hear your feedback on this new release. Join us on <a href="https://github.com/containous/traefik">GitHub</a>, <a href="https://twitter.com/traefikproxy">Twitter</a> or <a href="https://traefik.herokuapp.com/">Slack</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bc304a66ef3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/containous/traefik-1-2-morbier-is-out-8bc304a66ef3">Traefik 1.2 Morbier is out!</a> was originally published in <a href="https://medium.com/containous">containous</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>