<?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 Damien Duportal on Medium]]></title>
        <description><![CDATA[Stories by Damien Duportal on Medium]]></description>
        <link>https://medium.com/@damien_60655?source=rss-db88f00123cd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*unG5kgY7pKm1SmmO.jpg</url>
            <title>Stories by Damien Duportal on Medium</title>
            <link>https://medium.com/@damien_60655?source=rss-db88f00123cd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 17:02:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@damien_60655/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[Traefik and Docker: A Discussion with Docker Captain, Bret Fisher]]></title>
            <link>https://medium.com/containous/traefik-and-docker-a-discussion-with-docker-captain-bret-fisher-7f0b9a54ff88?source=rss-db88f00123cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f0b9a54ff88</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[docker-swarm]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Damien Duportal]]></dc:creator>
            <pubDate>Tue, 22 Oct 2019 06:01:01 GMT</pubDate>
            <atom:updated>2019-10-22T06:01:01.564Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_5MfuZcYX0CdT2QQHHKwHg@2x.png" /></figure><p>During the past summer, we had an interesting discussion about<a href="https://traefik.io/"> Traefik</a> and<a href="https://events.docker.com/events/details/docker-san-francisco-presents-traefik-v20-in-docker-containerd-updates/"> Docker</a> with Bret Fisher, the creator of “<a href="https://www.bretfisher.com/courses/">Docker Mastery</a>” and part of the<a href="https://www.docker.com/community/captains"> Docker Captain</a> program.</p><p>We’d like to share our discussion with you. Read on to learn more about Bret, and his experience using Traefik and Docker.</p><p><strong>Containous: Hi Bret, could you introduce yourself to our community?</strong></p><p><em>Bret: </em>Hi, I’m<a href="https://twitter.com/BretFisher"> Bret Fisher</a>, a freelance DevOps and Docker consultant, focused on containers. I’m also a Docker Captain. My time is split between teaching, helping students, answering questions.</p><blockquote><em>I’m driven by having fun while helping people.</em></blockquote><p><strong>Containous: Could you explain what is a “Docker Captain”?</strong></p><p><em>Bret: </em>The “Docker Captain” program is from Docker Inc.. A Docker Captain is like a Microsoft MVP. You cannot work for Docker Inc., should be an expert on docker tools and <strong>share</strong> your love for containers often. It also gives you access to pre-release Docker software.</p><p><strong>Containous: How did you get into Traefik?</strong></p><p><em>Bret: </em>Because of Docker Swarm mode. Even though Kubernetes has become the most popular orchestrator, Docker Swarm still solves a lot of problems for many team. I was searching for an easy “Ingress” for Docker Swarm and Traefik was recommended by a fellow Docker Captain.</p><blockquote><em>I liked Traefik because of the Let’s Encrypt support out-of-the box and because “It just works”.</em></blockquote><p><strong>Containous: Where do you use Traefik?</strong></p><p><em>Bret: </em>I’m using it on my own website at<a href="https://www.bretfisher.com/"> https://www.bretfisher.com/</a>. This website runs on Docker Swarm with Traefik. I also recommended Traefik to my customers, and in my talks and workshops. A lot of my 120,000 students have ended up using Traefik.</p><p><strong>Containous: Let’s talk a bit about container security. Are you running Traefik as the user “root”?</strong></p><p><em>Bret: </em>Is it the default ? (Laugh). I’m using the official Docker image so I guess “yes,” if it is the default user in that container Image.</p><p><strong>Containous: Do you see any compensation measure for this?</strong></p><p><em>Bret: </em>First of all, I have a <a href="https://github.com/BretFisher/ama/issues/17">list of general container security activities</a> that I follow and recommend others check out. It follows an order of “easiest steps with biggest benefits first” so you don’t spend time on hard security changes that have little overall improvement in your security posture. In addition, consider running Traefik’s container in<a href="https://docs.docker.com/engine/reference/commandline/run/#mount-volume--v---read-only"> “read-only” mode</a>. This mode forbids any writing on the filesystem (unless you explicitly define a volume on an explicit path.). This first step avoids some (but not all!) common tasks as installing packages or downloading scripts in case of a bad actor gaining file system control in the container. Also, you could enable the feature “user namespaces” in the Docker Engine config, to map the root user of containers to an unprivileged user of the host machines, which I’m a big fan of.</p><p>Running a Traefik container as a non privileged user to avoid being “root” might create two challenges:</p><ul><li>Listening on ports below 1024: the range of ports [0–1024] are privileged and thus require special capabilities. Either you can bind to port &gt; 1024, or ensure you are able to grant the Linux Capability CAP_NET_BIND_SERVICE to Traefik.</li><li>Docker socket membership: the socket file in /var/run/docker.sock is owned by the root user, and a group named docker. The unprivileged user of Traefik must be part of the group docker to allow access to the Docker API.</li></ul><p><strong>Containous: Speaking about the Docker socket, do you run Traefik on Swarm Manager Nodes?</strong></p><p><em>Bret: </em>It’s not mandatory. The point is — you can always forward the Docker socket through TCP instead of using a bind-mount of /var/run/docker.sock. If you forward the socket in TCP inside and encrypted Docker network, then it removes the “run on manager” constraint for Traefik.</p><p>Please note that overlay networks optional encryption is not performed by Docker Swarm itself, but rather the Linux kernel (IPSec), ensuring low-level security.</p><p>Also, it’s worthwhile to add an intermediate proxy to control requests through the TCP-forwarded Docker socket, allowing read-only requests to the API.</p><p>I have an <a href="https://github.com/BretFisher/dogvscat/blob/master/stack-proxy-global.yml">example Swarm stack YAML of this setup here</a>.</p><p>With all of these, running Traefik on the host network of worker nodes, with an overlay network for backends is totally doable.</p><p><strong>Containous: Are you using the Traefik dashboard? If yes, what is your point of view on the security of this feature?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kb8q6VKOvrvofb36" /><figcaption><strong>Traefik v2 Dashboard</strong></figcaption></figure><p><em>Bret: </em>Yes. I’m using the Traefik dashboard. I tend to configure the dashboard with an IP whitelist, and not exposed on a public network or on the default port.</p><p>Publicly exposing an admin dashboard keeps happening: just look at situations such as the<a href="https://redlock.io/blog/cryptojacking-tesla"> Kubernetes dashboard hack at Tesla</a>.</p><p>I’m a huge fan of “secure by default” tools, and I wished more tools were like Docker and Swarm in this way. Over my 25 years in tech helping many companies with infrastructure, I’ve learned that if authentication and encryption are optional, many won’t do it.</p><p><strong>Containous: Do you have a recommendation about using the “default” Docker image for Traefik based on “scratch” versus the “Linux Alpine” image? Why?</strong></p><p><em>Bret: </em>As a rule of thumb, I would avoid “scratch” (or <a href="https://github.com/GoogleContainerTools/distroless">distroless</a>) images until everyone in the pipeline is able to know how to operate it. Size is not important unless you’re operating an IoT business. Compared to the pain and suffering of “no tools,” using “scratch” doesn’t feel a good trade-off unless you have specialists on board. The image “scratch” feels like a “Golang developers” habit, but when it comes to the Ops team it’s another topic: What about not being able to docker exec or kubectl cp?</p><p>Hopefully, the <a href="https://kubernetes.io/docs/concepts/workloads/pods/ephemeral-containers/">Kubernetes ephemeral containers</a> feature will help make this possible for more people.</p><p>As a rule of thumb, for container newcomers, they need to learn by doing. In this case, I wouldn’t use “scratch” here to keep the learning curve smooth.</p><p>I also share this opinion about the host OS. Too many people try to use a “Container OS” too early in their organisational learning. It tends to add lots of risk without a big productivity boost. Stick with your traditional Linux distribution until you’ve had significant production Docker usage.</p><p><strong>Containous: What is your recommendation for the load balancer part outside Swarm? To create an external load balancer pointing to nodes, using DNS, or something else? And, why?</strong></p><p><em>Bret: </em>The expected answer is “It’s complicated” or ”It depends” (laugh).</p><p>Most companies already have their own solution for load balancing, including cloud load balancers and datacenter hardware load balancers. Then they point their load balancer to the Docker Swarm nodes and rely on Traefik for providing the application layer load balancing inside the cluster. Pro Tip: Don’t point LB’s to all your Swarm nodes. Pick 2–3 worker nodes and make those the ingress points, which will make troubleshooting and load easier to manage.</p><p>However, about the “DNS round robin” solution, I refer to it as the “poor person’s LB”, because of the small amount of time required to make it work. It’s simple when the client is a web browser, but as you cannot control the “client”, that’s where the limit is drawn (DNS caching, no retry patterns, etc.). Another limit: as soon as showing HTTP 503 errors is an issue, there is no “retry pattern” expected from web browsers (even though Traefik could do that). It’s the recommended solution in my course “Solo DevOps” where the context is “only one person in charge of the DevOps tasks, with so many tools involved”. Once you have an external load balancer solution, it’s likely best to stick with that in all but the smallest projects.</p><p>As a general rule, ask yourselves: “During the time it goes down, do you lose money? If yes, then go for load balancing with health checks.”</p><blockquote><em>Try both solutions for education purposes. It’s really valuable.</em></blockquote><p><strong>Containous: Have you tried the new</strong><a href="https://blog.containo.us/traefik-2-0-6531ec5196c2"><strong> Traefik v2.0</strong></a><strong>?</strong></p><p><em>Bret: </em>Not yet, but it made quite some noise in the Docker Captain channel. It might be the fact that they are “Golang people,” but it looks neat.</p><p><strong>Containous: Is there something you would like to tell the Traefik community?</strong></p><p><em>Bret: </em>Traefik is a really nice tool because everything is configurable from the command line when starting in a container (using CMD). TOML files are fine, but it’s great to have the option to skip that and configure it dynamically at runtime.</p><p>Also, everything is streamlined for the container world, with a linear learning curve: configuration management is not mandatory even for rich features such as Let’s Encrypt.</p><p><strong>Containous: Thanks a lot for these insights Bret! Happy to have this exchange. Let’s meet again for a live session next time!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f0b9a54ff88" width="1" height="1" alt=""><hr><p><a href="https://medium.com/containous/traefik-and-docker-a-discussion-with-docker-captain-bret-fisher-7f0b9a54ff88">Traefik and Docker: A Discussion with Docker Captain, Bret Fisher</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[Announcing Maesh, a Lightweight and Simpler Service Mesh Made by the Traefik Team]]></title>
            <link>https://medium.com/containous/announcing-maesh-a-lightweight-and-simpler-service-mesh-made-by-the-traefik-team-cb866edc6f29?source=rss-db88f00123cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb866edc6f29</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[service-mesh]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Damien Duportal]]></dc:creator>
            <pubDate>Wed, 04 Sep 2019 12:55:28 GMT</pubDate>
            <atom:updated>2019-09-04T12:55:28.131Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2_BDgPxbXlrkdgxABCMnYQ@2x.png" /></figure><p>We are proud to introduce <a href="http://mae.sh/">Maesh</a>, Containous’ new service mesh designed from the ground up to be straightforward, easy to install and easy to use. Maesh allows for visibility and management of the traffic that flows inside your Kubernetes cluster, which is just as important as the ingress and egress traffic.</p><p>Built on top of Traefik, Maesh is a simple, yet full-featured service mesh. It is container-native and fits as your de-facto service mesh in your Kubernetes cluster. It supports the latest Service Mesh Interface specification (<a href="https://smi-spec.io/">SMI</a>) that facilitates integration with pre-existing solutions. Moreover, Maesh is opt-in by default, which means that your existing services are unaffected until you decide to add them to the mesh.</p><h3>Non-Invasive Service Mesh</h3><p>Maesh does not use any sidecar container but handles routing through proxy endpoints running on each node. The mesh controller runs in a dedicated pod and handles all the configuration parsing and deployment to the proxy nodes. Maesh supports multiple configuration options: annotations on user service objects, and SMI objects. Not using sidecars means that Maesh does not modify your Kubernetes objects, and does not modify your traffic without your knowledge. Using the Maesh endpoints is all that is required.</p><figure><img alt="Maesh Architecture" src="https://cdn-images-1.medium.com/max/1024/1*HEiqaSQ_gI-P_b3nRU-MBA.jpeg" /><figcaption>Maesh Architecture</figcaption></figure><h3>Relies on Kubernetes DNS</h3><p>Maesh leverages the <a href="https://coredns.io/">CoreDNS</a> platform installed by default in Kubernetes. It allows users to use the Maesh endpoints (instead of the standard Kubernetes service endpoints) to benefit from its feature set — no sidecars! Maesh endpoints run side-by-side with user services: you choose whether you use them or not (opt-in). This gives more confidence, since users know that they are able to test, and revert back to the user services: they should be happy with the result.</p><p>Also, the updates to CoreDNS made during the installation of Maesh is minimal and non-invasive, and is easily removable.</p><h3>Multiple Network Layers</h3><p>Maesh can run in both TCP and HTTP mode</p><ul><li>In HTTP mode, Maesh leverages Traefik’s feature set to enable rich routing on virtual-host, path, headers, cookies.</li><li>Using TCP mode allows a seamless and easy integration with SNI routing support.</li></ul><p>Use both modes at the same time within the same cluster, and is configurable via annotations on services.</p><h3>Built on Top of Traefik</h3><p>Maesh builds on top of <a href="https://traefik.io/">Traefik</a>, the leading reverse proxy for routing, and provides every feature users would expect: OpenTracing, load balancing for HTTP, gRPC, WebSocket, TCP, rich routing rules, retries and fail-overs, not to mention access controls, rate limits, and circuit breakers.</p><h3>Easy to Install; Easy to Use</h3><p>Installing Maesh to your cluster is easy: install the Helm chart, as there are no helper applications, no CRDs to install, and no new vocabulary for users to learn. If users understand how pods and services work, then Maesh will be easy to understand and use.</p><p>Let’s get started by installing Maesh using the following commands:</p><pre>$ helm repo add maesh <a href="https://containous.github.io/maesh/charts">https://containous.github.io/maesh/charts</a><br>$ helm repo update<br>$ helm install --name=maesh --namespace=maesh maesh/maesh</pre><p>Maesh is now ready to use in your cluster, and you’re one annotation away from using it on any running application:</p><pre>$ kubectl annotate service \<br>    web-application maesh.containo.us/traffic-type=http</pre><p>Is your application using a TCP communication protocol (which is not HTTP)? It is also supported:</p><pre>$ kubectl annotate service mongo-database \<br>    maesh.containo.us/traffic-type=tcp</pre><p>That’s how easy it is to install and use Maesh!</p><h3>What’s Next</h3><p>Because Maesh is open source, we would love the community’s input as to which features are important to you, so that we can prioritise the top requests.</p><p>We welcome community contributions and love when they are faster than us to provide additional features! Pull requests are the best way to support the product and make it your own.</p><p><strong>Useful links</strong></p><ul><li><a href="http://mae.sh/">Website</a></li><li><a href="http://docs.mae.sh/">Documentation</a></li><li><a href="https://github.com/containous/maesh">Github</a></li><li><a href="https://community.containo.us/c/maesh">Community Forum</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb866edc6f29" width="1" height="1" alt=""><hr><p><a href="https://medium.com/containous/announcing-maesh-a-lightweight-and-simpler-service-mesh-made-by-the-traefik-team-cb866edc6f29">Announcing Maesh, a Lightweight and Simpler Service Mesh Made by the Traefik Team</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[The Journey to Traefik Enterprise Edition: Smooth Operations]]></title>
            <link>https://medium.com/containous/the-journey-to-traefik-enterprise-edition-smooth-operations-2591bb7ff1fe?source=rss-db88f00123cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/2591bb7ff1fe</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[deployment]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Damien Duportal]]></dc:creator>
            <pubDate>Mon, 18 Mar 2019 12:01:03 GMT</pubDate>
            <atom:updated>2019-03-18T12:01:03.146Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Image result for traefik" src="https://cdn-images-1.medium.com/proxy/1*FA-ZxO_2HjFO9sJpBE1SEw.png" /></figure><p>Welcome to the fifth step of our journey towards <a href="https://containo.us/traefikee">Traefik Enterprise Edition</a>.</p><p>This post focuses on the experience of operating TraefikEE using the traefikeectl command line. You should already feel at ease with TraefikEE’s one-line installation and concepts. If you are not, then you can check the previous posts of the “Journey to TraefikEE:”</p><ul><li><a href="https://blog.containo.us/the-journey-to-traefik-enterprise-edition-join-the-early-access-program-b73e07d62f30"><em>Join the“Early Access” Program</em></a></li><li><a href="https://blog.containo.us/the-journey-to-traefik-enterprise-edition-product-evaluation-4828508cbc8"><em>Product Evaluation</em></a></li><li><a href="https://blog.containo.us/the-journey-to-traefik-enterprise-edition-high-availability-7421718be2d8"><em>High Availability</em></a></li><li><a href="https://blog.containo.us/the-journey-to-traefik-enterprise-edition-https-for-everyone-90a36b33600"><em>HTTPS for Everyone</em></a></li></ul><p>Today, we’ll focus on traefikeectl, the command-line tool used to install, configure and operate all your TraefikEE installations, in a lean and repeatable way, independently of your platform.</p><h3>One Command-Line to Rule Them All</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/277/0*pKYNsD-OIeW66GY9.png" /></figure><blockquote><strong>(A voice in the background):</strong> I used Traefik because it’s really simple to use. I’m interested by TraefikEE for its high availability features. But distributed systems are really hard. How to deal with this intrinsic complexity?</blockquote><blockquote><strong>Containous:</strong> Let us introduce <em>traefikeectl</em> (also known as “TraefikEE-cuddle”), the command-line tool which abstracts most of this complexity.</blockquote><p>TraefikEE is designed from the ground up to be platform agnostic. From installation to any operation, the workflow is the same on each platform.</p><p>All the operations are managed by the command line traefikeectl following this workflow, whichever platform you are using:</p><ul><li><strong>Install Phase:</strong> Installs a TraefikEE cluster (with traefikeectl install or manually),</li><li><strong>Connect Phase: </strong>Make your local traefikeectl aware of an existing TraefikEE cluster allowing multi-cluster management,</li><li><strong>Deploy Phase:</strong> Deploy a “routing configuration” to this TraefikEE instance.</li></ul><h3>Install Phase</h3><h4>Platform-Specific</h4><p>Do you remember the <a href="https://blog.containo.us/the-journey-to-traefik-enterprise-edition-product-evaluation-4828508cbc8#23cd">“One Line Installation for Kubernetes”</a> from previous posts (and the <a href="https://docs.containo.us/installation-guides/kubernetes/oneline/">related documentation</a>)?</p><pre>$ traefikeectl install \<br>  --licensekey=&quot;$(cat /keybase/.../traefikee-license)&quot; \<br>  --dashboard \<br>  --kubernetes<br>...</pre><p>What if you want to install on a Docker Swarm cluster instead?</p><p>Well, the answer is to use the flag —-swarm instead of --kubernetes , as described on the <a href="https://docs.containo.us/installation-guides/swarm/oneline/">“One Line Installation guide for Swarm”</a>:</p><pre>$ traefikeectl install \<br>  --licensekey=&quot;$(cat /keybase/.../traefikee-license)&quot; \<br>  --dashboard \<br>  --swarm<br>...</pre><p>Each “agnostic” feature is then provided by the commandtraefikeectl when required, as --kubernetes.namespace or --swarm.networkname .</p><h4>Customize Installation</h4><p>We’ll now dig on how to customize installation for Kubernetes.</p><blockquote><strong>(A voice in the background):</strong> We are not able to use <em>traefikeectl</em> for installation in our Kubernetes cluster, because the default configuration does not fit our needs.</blockquote><blockquote><strong>Containous:</strong> The <em>install</em> command of <em>traefikeectl</em> allows you to customize installation. With Kubernetes, you can provide a YAML file to specify custom values.</blockquote><p>Following <a href="https://docs.containo.us/references/configs/helm/#configuration-items-reference">the reference values from the documentation</a>, let’s consider that you want to specify the following elements during the installation:</p><ul><li>A custom URL for accessing the dashboard, as http(s)://private.mycompany.org/traefikee,</li><li>Limiting the resources used for each node to 2Gb of memory and 2 CPUs (See the article “<a href="https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/">Managing Compute Resources for Containers</a>” Kubernetes Documentation for reference).</li></ul><p>Before installation, create the following YAML file to specify these values:</p><pre>## traefikee-values.yaml</pre><pre># Expose dashboard at http(s)://private.mycompany.org/traefikee<br>dashboard:<br>  host: &quot;private.mycompany.org&quot;<br>  path: &quot;/traefikee&quot;</pre><pre># Restrict resources usage for each TraefikEE node<br>resources:<br>  cpus: &quot;2&quot;<br>  memory: &quot;2G&quot;</pre><p>You can now proceed to the “One Line Installation”, by adding the flag --kubernetes.helmvaluespath to use the YAML value file:</p><pre>traefikeectl install --kubernetes \<br>  --licensekey=XXXXXXX \<br>  --dashboard \<br>  --kubernetes.helmvaluespath=./traefikee-values.yaml</pre><p>As no one is perfect, traefikeectl might not provide some specific settings required for your platform to work correctly. In this case, you still can “<a href="https://kubernetes.io/docs/reference/kubectl/cheatsheet/#patching-resources">patch</a>” , <a href="https://kubernetes.io/docs/reference/kubectl/cheatsheet/#editing-resources">“edit”</a> or even <a href="https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#annotate">“annotate”</a> the Kubernetes resources created by traefikee install.</p><h3>Connect Phase</h3><p>The next step is to ensure that your traefikeectl command has knowledge of the cluster you want to operate.</p><blockquote>Please note that this step is not required if you used a “One Line Installation” with traefikeectl install, as it is automatically done.</blockquote><p>The scenario is the following:</p><ul><li>A TraefikEE cluster, designated astraefikee-staging, is running on your remote Kubernetes platform, in the namespace traefikee-ingress,</li><li>You want to set up an administration machine (your computer, a freshly onboarded team member, etc.) to operate this cluster,</li><li>This machine is already configured to reach the Kubernetes cluster.</li></ul><p>The connect phase is easy:</p><pre>traefikeectl connect --clustername=traefikee-staging \<br>  --kubernetes \<br>  --kubernetes.namespace=traefikee-ingress</pre><p>That’s all: traefikeectl is now aware of this cluster and can operate it:</p><pre>$ traefikeectl list-nodes<br>$ traefikeectl logs<br>...</pre><p>Under the hood, traefikeectl stored the cluster connection information in a TOML file named after the cluster name. These files are located in ${TRAEFIKEE_HOME}, which defaults to the directory ${HOME}/.config/traefikee (<a href="https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html">XDG_CONFIG folder</a>).</p><blockquote>Please note that if you do not provide the option --clustername , the default value traefikee is used.</blockquote><p>It means that you can manage multiple TraefikEE clusters from the same traefikeectl, so you are free to split per environment (staging/production, or event external/internal, etc.).</p><h3>Deploy Phase</h3><p>The last step of the workflow is to deploy a “<a href="https://docs.containo.us/references/configs/routing/">routing configuration</a>”.</p><blockquote><strong>(A voice in the background):</strong> We followed the previous blog post, and we were able to install TraefikEE on our platform. Now, we want to enable HTTPS and Metrics collection with <a href="https://prometheus.io/">Prometheus</a>. Do we have to install the cluster again to update the configuration as we did for Traefik?</blockquote><blockquote><strong>Containous:</strong> Fortunately, you don’t have to reinstall the cluster. Unlike Traefik, TraefikEE lets you update the configuration at runtime.</blockquote><p>Let’s say that you want to set up TraefikEE with the following routing configuration:</p><ul><li>Enable TLS termination on the port 443 (defining a new “entrypoint” named https),</li><li>Auto-generate TLS certificates using Let’s Encrypt for this new https “entrypoint” . The host names for these certificates are determined from the backend applications (either Ingresses on Kubernetes or labels on Docker Swarm),</li><li>Enable the Prometheus metric exporter,</li><li>Enable redirection from http to https for any incoming request.</li></ul><p>With Traefik, you would have passed the following options (and restarted Traefik to apply the configuration):</p><pre>## Traefik Configuration References:<br># Entrypoints: <a href="https://docs.traefik.io/configuration/entrypoints/">https://docs.traefik.io/configuration/entrypoints/</a><br># Metrics: <a href="https://docs.traefik.io/configuration/metrics/">https://docs.traefik.io/configuration/metrics/</a><br># ACME/Let&#39;s Encrypt: <a href="https://docs.traefik.io/configuration/acme/">https://docs.traefik.io/configuration/acme/</a></pre><pre>traefik --kubernetes \<br>  --entryPoints=&#39;Name:http Address::80 Redirect.EntryPoint:https&#39; \<br>  --entryPoints=&#39;Name:https Address::443 TLS&#39; \<br>  --defaultentrypoints=https,http \<br>  --acme.entryPoint=https \<br>  --<a href="/service/mailto:acme.email=damien@containo.us">acme.email=damien@containo.us</a> \<br>  --acme.tlsChallenge \<br>  --acme.onHostRule=true \<br>  --metrics.prometheus</pre><p>With TraefikEE, the same configuration is passed to the traefikeectl deploy command. It’s sent to the TraefikEE control plane through the traefikeectl API, stored on the TraefikEE Control Plane and then applied to <strong>all</strong> the TraefikEE Data Nodes (which are hot-reloaded).</p><pre>traefikeectl deploy --kubernetes \<br>  --entryPoints=&#39;Name:http Address::80 Redirect.EntryPoint:https&#39; \<br>  --entryPoints=&#39;Name:https Address::443 TLS&#39; \<br>  --defaultentrypoints=https,http \<br>  --acme.entryPoint=https \<br>  --<a href="/service/mailto:acme.email=damien@containo.us">acme.email=damien@containo.us</a> \<br>  --acme.tlsChallenge \<br>  --acme.onHostRule=true \<br>  --metrics.prometheus</pre><p>If you prefer using TOML file instead of command-line flags:</p><pre>$ cat traefik.toml</pre><pre>defaultEntryPoints = [&quot;https&quot;,&quot;http&quot;]</pre><pre>[entryPoints]<br>  [entryPoints.http]<br>  address = &quot;:80&quot;<br>    [entryPoints.http.redirect]<br>    entryPoint = &quot;https&quot;<br>  [entryPoints.https]<br>  address = &quot;:443&quot;<br>  [entryPoints.https.tls]</pre><pre>[kubernetes]</pre><pre>[acme]<br>email = &quot;<a href="/service/mailto:damien@containo.us">damien@containo.us</a>&quot;<br>storage = &quot;acme.json&quot;<br>entryPoint = &quot;https&quot;<br>onHostRule = true<br>[acme.tlsChallenge]</pre><pre>$ traefikeectl deploy --configfile=./traefik.toml</pre><p>That’s all for today: we installed a customized cluster, connected a remote machine to operate with traefikeectl, and deployed the same configuration as the one you could have used for Traefik, but without taking down the cluster, and without loosing any requests!</p><p>You can learn more about the traefikeectl command line on <a href="https://docs.containo.us/references/cli/traefikeectl/">the reference documentation</a>.</p><p>On the next post, “The Journey to Traefik Enterprise Edition: Backup and Restore” we’ll focus on how to save the configuration of your TraefikEE cluster, and how to re-install it from a backup to handle control plane failures.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2591bb7ff1fe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/containous/the-journey-to-traefik-enterprise-edition-smooth-operations-2591bb7ff1fe">The Journey to Traefik Enterprise Edition: Smooth Operations</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[The Journey to Traefik Enterprise Edition: HTTPS for Everyone]]></title>
            <link>https://medium.com/containous/the-journey-to-traefik-enterprise-edition-https-for-everyone-90a36b33600?source=rss-db88f00123cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/90a36b33600</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[distributed-systems]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Damien Duportal]]></dc:creator>
            <pubDate>Mon, 25 Feb 2019 15:31:00 GMT</pubDate>
            <atom:updated>2019-02-25T15:31:00.832Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*0Gu7W6KCr373QH4be5ShWQ.png" /></figure><p>Welcome to the fourth step of our journey towards <a href="https://containo.us/traefikee">Traefik Enterprise Edition</a>.</p><p>Before jumping in, you should check the previous posts:</p><ul><li><a href="https://blog.containo.us/the-journey-to-traefik-enterprise-edition-join-the-early-access-program-b73e07d62f30"><em>Join the“Early Access” Program</em></a></li><li><a href="https://blog.containo.us/the-journey-to-traefik-enterprise-edition-product-evaluation-4828508cbc8"><em>Product Evaluation</em></a></li><li><a href="https://blog.containo.us/the-journey-to-traefik-enterprise-edition-high-availability-7421718be2d8"><em>High Availability</em></a></li></ul><p>Today, we’ll focus on how to use TraefikEE with Let’s Encrypt to get HTTPS by default, for your application.</p><h3>Create a Kubernetes Cluster with kops</h3><p>Following the same steps as <a href="https://blog.containo.us/the-journey-to-traefik-enterprise-edition-high-availability-7421718be2d8#e422">the previous blog post (“Create a cluster with kops”)</a>, start a kops cluster with one Kubernetes manager and three Kubernetes nodes:</p><pre>$ export NAME=traefikee-demo.containous.cloud<br>$ export KOPS_STATE_STORE=s3://&lt;YOUR BUCKET&gt;<br>$ export ROUTE53_ZONE_ID=&lt;ROUTE53_ZONE_ID&gt;</pre><pre>$ export NB_MASTER_NODE=1<br>$ export NB_WORKER_NODE=3</pre><pre>$ kops create cluster \<br>    --zones us-east-1a \<br>    --dns-zone=&quot;${ROUTE53_ZONE_ID}&quot; \<br>    --node-size=&quot;t2.large&quot; \<br>    --master-count=&quot;${NB_MASTER_NODE}&quot; \<br>    --node-count=&quot;${NB_WORKER_NODE}&quot; \<br>    --yes \<br>    &quot;${NAME}&quot;</pre><p>After a few minutes, your cluster is started with four Kubernetes nodes:</p><pre>$ kubectl get nodes<br>NAME                            STATUS   ROLES    AGE   VERSION<br>ip-172-20-34-251.ec2.internal   Ready    node     2m    v1.11.6<br>ip-172-20-49-209.ec2.internal   Ready    node     2m    v1.11.6<br>ip-172-20-53-165.ec2.internal   Ready    node     2m    v1.11.6<br>ip-172-20-56-217.ec2.internal   Ready    master   3m    v1.11.6</pre><h3>Pick a Public Domain Name</h3><p>In the previous blog post, we used <a href="https://blog.containo.us/the-journey-to-traefik-enterprise-edition-high-availability-7421718be2d8">a domain name generated by Amazon Web Services</a> as the main entry point to reach our platform.</p><p>You cannot use this “generated” public hostname, because Let’s Encrypt has a “forbidden domains list.” Some domains are considered too risky, and any request for issuing certificates under these domains is automatically refused. <a href="https://community.letsencrypt.org/t/policy-forbids-issuing-for-name-on-amazon-ec2-domain/12692/2">It’s the case with domains in </a><a href="https://community.letsencrypt.org/t/policy-forbids-issuing-for-name-on-amazon-ec2-domain/12692/2">*.amazonaws.com</a>.</p><p>To solve this challenge, let’s pick a custom public domain name. Any domain or sub-domain (like test.company.org ) can be used. You have to be able to create DNS records of type CNAME on this domain.</p><blockquote><strong>(A voice in the background):</strong> I don’t want to pay for a domain used for evaluating a product. Maybe later if it goes further, but not now.</blockquote><blockquote><strong>Containous:</strong> You can get free DNS using <a href="http://www.dot.tk/en/index.html?lang=en">Dot-T-K</a>, or even cheap ones using <a href="https://www.namecheap.com/">NameCheap</a>.</blockquote><p>For the next steps, we’ll pick the domain demo.containo.us .</p><h3>Install TraefikEE</h3><p>Then, install a simple TraefikEE cluster, without dashboard, as we did on <a href="https://blog.containo.us/the-journey-to-traefik-enterprise-edition-high-availability-7421718be2d8#bc5b">the previous blog post</a>:</p><pre>$ traefikeectl install \<br>  --licensekey=&quot;$(cat /keybase/…/traefikee-license)&quot; \<br>  --kubernetes<br>...</pre><pre>✔ Installation successful</pre><p>Once the installation succeeded, verify that the TraefikEE cluster is composed of six nodes, three control nodes and three data nodes, as expected:</p><pre>$ traefikeectl list-nodes<br>...<br>Name                                 Role<br>----                                 ----<br>traefikee-control-node-0             CONTROL NODE<br>data-node-traefikee-data-node-9ndbp  DATA NODE<br>data-node-traefikee-data-node-vqgzr  DATA NODE<br>traefikee-control-node-1             CONTROL NODE<br>traefikee-control-node-2             CONTROL NODE (Current Leader)<br>data-node-traefikee-data-node-5w66x  DATA NODE</pre><h3>Configure the Domain DNS Records</h3><p>The next step is to create a CNAME DNS record, on the public domain name, pointing to the Load Balancer’s hostname, created during TraefikEE’s installation.</p><p>Get the load balancer’s public hostname with the following command (field EXTERNAL-IP):</p><pre>$ kubectl get svc -n traefikee traefikee-lb<br>NAME          TYPE         EXTERNAL-IP<br>traefikee-lb  LoadBalancer a16ff-456.us-east-1.elb.amazonaws.com</pre><p>Then, create the DNS CNAME record to this hostname (choose a short TTL):</p><pre>IN  CNAME  demo.containo.us a16ff-456.us-east-1.elb.amazonaws.com</pre><p>The DNS propagation takes some time, due to the “TTL”. Verify that your computer can resolve the DNS name with tools asdig , drillor nslookup :</p><pre>$ dig CNAME demo.containo.us<br>...<br>;; QUESTION SECTION:<br>;demo.containo.us.       IN      CNAME</pre><pre>;; ANSWER SECTION:<br>demo.containo.us. 60     IN      CNAME   a16ff-456.us-east-1.elb.amazonaws.com.</pre><pre>;; Query time: 38 msec<br>;; SERVER: 212.224.255.252#53(212.224.255.252)<br>;; WHEN: Wed Feb 06 11:21:25 CET 2019<br>;; MSG SIZE  rcvd: 136</pre><h3>Configure TraefikEE for HTTPS</h3><p>Then, we configure TraefikEE to enable HTTPS and Let’s Encrypt for certificate on HTTPS. The configuration is the same as Traefik’s (check <a href="https://docs.traefik.io/configuration/acme/">Traefik’s documentation on ACME / Let’s Encrypt</a> for more details):</p><pre>### Configure 2 entrypoints for https and https<br>  --entryPoints=&#39;Name:http Address::80 Redirect.EntryPoint:https&#39; \<br>  --entryPoints=&#39;Name:https Address::443 TLS&#39; \<br>  --defaultentrypoints=https,http \</pre><pre>### Enable ACME protocol for the HTTPS entry point<br>  --acme.entryPoint=https \</pre><pre>### Set up ACME protocol for Let&#39;s Encrypt TLS-APLN-01 Challenge<br>  --<a href="/service/mailto:acme.email=damien@containo.us">acme.email=damien@containo.us</a> \<br>  --acme.tlsChallenge \</pre><pre>### Tell Traefik to get certificate&#39;s hostname from backend&#39;s rules<br>  --acme.onHostRule=true</pre><blockquote><strong>(A voice in the background):</strong> When using Traefik with Let’s Encrypt, I often get certificates requests failures because of <a href="https://letsencrypt.org/docs/rate-limits/">the rate limit on Let’s Encrypt side</a>.</blockquote><blockquote><strong>Containous:</strong> Traefik allows to test your HTTPS configuration with <a href="https://letsencrypt.org/docs/staging-environment/">the “staging” environment</a>, without rate limiting, but with untrusted certificates . It’s useful to validate configuration before switching to “production” certificates. Add the flag --acme.caServer=&#39;https://acme-staging-v02.api.letsencrypt.org/directory<em>&#39; to the configuration.<br>Be careful! You cannot change the caServer unless you reinstall TraefikEE.</em></blockquote><p>The main difference from using Traefik here, is that TraefikEE is a distributed system, so you need to specify the configuration <strong>after</strong> TraefikEE’s installation.</p><p>The traefikeectl tool provides a command named deploy to send any routing configuration to the TraefikEE cluster. You can read more on this topic on the <a href="https://docs.containo.us/references/configs/routing/">reference documentation for routing configurations</a>.</p><p>Now, let’s deploy the following configuration to the TraefikEE cluster and that’s all!</p><pre>traefikeectl deploy --kubernetes \<br>  --entryPoints=&#39;Name:http Address::80 Redirect.EntryPoint:https&#39; \<br>  --entryPoints=&#39;Name:https Address::443 TLS&#39; \<br>  --defaultentrypoints=https,http \<br>  --acme.entryPoint=https \<br>  --<a href="/service/mailto:acme.email=damien@containo.us">acme.email=damien@containo.us</a> \<br>  --acme.tlsChallenge \<br>  --acme.onHostRule=true</pre><blockquote><strong>(A voice in the background):</strong> Why is there a —-kubernetes flag in this configuration?</blockquote><blockquote><strong>Containous:</strong> This flag tells TraefikEE to watch for any Kubernetes Ingress. It’s the same directive as <a href="https://docs.traefik.io/configuration/backends/kubernetes/">the one in Traefik</a>.</blockquote><h3>Deploy an Application</h3><p>As we previously did on the post, “A Tour of TraefikEE”, we deploy a test application based on <a href="https://github.com/containous/whoami">https://github.com/containous/whoami</a>.</p><p>You can reuse the same <a href="https://gist.githubusercontent.com/dduportal/ad5e68ffcd9e39c65bdf4af7224304a0/raw/8b87143b084c612f86d66f587df7c058c7fa1aa0/whoami.yaml">YAML file</a>, but you have to change the directive host in the ingress, and map it to your public domain name. I’m using the following one-line shell command for this:</p><pre>$ curl --location --silent --show-error <a href="https://bit.ly/2WE5XFk">https://bit.ly/2WE5XFk</a> \<br>  | sed &#39;s/localhost/demo.damienduportal.org/g&#39; \<br>  | kubectl apply -f -</pre><pre>deployment.extensions/whoami created<br>ingress.extensions/whoami created<br>service/whoami created</pre><p>You can check that Kubernetes is using the right domain name by checking the ingress “whoami”:</p><pre>$ kubectl get ingress whoami --namespace=traefikee<br>NAME     HOSTS                     ADDRESS   PORTS   AGE<br>whoami   demo.damienduportal.org             80      9m</pre><p>The page <a href="https://demo.damienduportal.org/whoami">https://demo.damienduportal.org/whoami</a> is now, (after a few seconds, required for issuing certificates), securely served over HTTPS, with a valid certificate, issued by Let’s Encrypt:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/761/1*qOVKiNvq_r7Ra1-Wgv6tRg.png" /><figcaption>Green Lock for Everyone</figcaption></figure><blockquote>If you try to access <a href="http://demo.damienduportal.org/whoami">http://demo.damienduportal.org/whoami</a>, then you are redirected to <a href="https://demo.damienduportal.org/whoami">https://demo.damienduportal.org/whoami</a> as expected.</blockquote><p>That’s all for today, you are ready to use HTTPS on your applications! <br>You can now clean your kops cluster with:</p><pre>kops delete cluster --name=&quot;${NAME}&quot;</pre><p>On the next post, “The Journey to Traefik Enterprise Edition: Smooth Operations,” we’ll focus on how to configure and operate TraefikEE remotely with the traefikeectl command line.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90a36b33600" width="1" height="1" alt=""><hr><p><a href="https://medium.com/containous/the-journey-to-traefik-enterprise-edition-https-for-everyone-90a36b33600">The Journey to Traefik Enterprise Edition: HTTPS for Everyone</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[The Journey to Traefik Enterprise Edition: High Availability]]></title>
            <link>https://medium.com/containous/the-journey-to-traefik-enterprise-edition-high-availability-7421718be2d8?source=rss-db88f00123cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/7421718be2d8</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[traefik]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Damien Duportal]]></dc:creator>
            <pubDate>Mon, 28 Jan 2019 16:31:00 GMT</pubDate>
            <atom:updated>2019-01-28T16:31:00.655Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ae373mdbxxi0vRyNn4MT_w.png" /></figure><p>Welcome to the third step of our journey towards<a href="https://containo.us/traefikee"> Traefik Enterprise Edition</a> .</p><p>After the two first posts <a href="https://blog.containo.us/the-journey-to-traefik-enterprise-edition-join-the-early-access-program-b73e07d62f30"><em>Join the“Early Access” Program</em></a>, and <a href="https://blog.containo.us/the-journey-to-traefik-enterprise-edition-product-evaluation-4828508cbc8"><em>Product Evaluation</em></a>), let’s get real and evaluate TraefikEE’s high availability feature.</p><p>The previous post described how to install TraefikEE on a local machine, which is not a realistic environment. Today, we’ll use a Kubernetes multi-node cluster deployed in Amazon EC2 as a more realistic platform for running TraefikEE.</p><h3>Creating a Kubernetes Cluster with kops</h3><p>The first step is to get a multi-node Kubernetes cluster up and running somewhere in the cloud.</p><p>kops (aka. “Kubernetes Operations”) is a tool provided by the Kubernetes community. It provides a command line to create and manage Kubernetes clusters on cloud infrastructures as <a href="https://aws.amazon.com/ec2/">Amazon EC2</a>, <a href="https://cloud.google.com/compute/?hl=fr">Google Compute Engine</a> or <a href="https://www.digitalocean.com/">Digital Ocean</a>.</p><p>Using the <a href="https://github.com/kubernetes/kops/blob/master/docs/aws.md#configure-dns">kops tutorial for AWS</a>, we have the following requirements set up:</p><ul><li>The aws command line tool installed</li><li>AWS API access credentials loaded (<a href="https://github.com/mmatur/aws-mfa">check this project</a> from <a href="https://medium.com/u/c01753d22e74">Michael MATUR</a> if you need MFA)</li><li>The kops command line tool installed</li><li>One of the 3 DNS scenarios configured</li><li>An AWS S3 bucket created to store kops configuration</li></ul><p>We can create a Kubernetes cluster with 3 masters and 6 worker nodes. The worker nodes are a <a href="https://aws.amazon.com/ec2/instance-types/t2/">t2.large</a> types, with 2 CPUs and 8 Gb memory each:</p><pre>$ export NAME=traefikee-demo.containous.cloud<br>$ export KOPS_STATE_STORE=s3://&lt;YOUR BUCKET&gt;<br>$ export ROUTE53_ZONE_ID=&lt;ROUTE53_ZONE_ID&gt;</pre><pre>$ kops create cluster \<br>  --zones us-east-1a \<br>  --dns-zone=&quot;${ROUTE53_ZONE_ID}&quot; \<br>  --node-size=&quot;t2.large&quot; \<br>  --master-count=3 \<br>  --node-count=6 \<br>&quot;${NAME}&quot;</pre><p>Once the cluster is created, validate its state with kops, and verify the access to the Kubernetes API with the kubectl:</p><pre>$ kops validate cluster --name=&quot;${NAME}&quot;<br>Validating cluster traefikee-demo.containous.cloud<br>...</pre><pre>Your cluster traefikee-demo.containous.cloud is ready</pre><pre>$ kubectl get nodes<br>NAME STATUS ROLES AGE VERSION<br>ip-172–20–33–152.ec2.internal Ready node 1d v1.11.6<br>ip-172–20–37–195.ec2.internal Ready master 1d v1.11.6<br>ip-172–20–38–193.ec2.internal Ready node 1d v1.11.6<br>ip-172–20–42–46.ec2.internal Ready master 1d v1.11.6<br>ip-172–20–44–104.ec2.internal Ready node 1d v1.11.6<br>ip-172–20–52–184.ec2.internal Ready node 1d v1.11.6<br>ip-172–20–60–90.ec2.internal Ready node 1d v1.11.6<br>ip-172–20–61–254.ec2.internal Ready node 1d v1.11.6<br>ip-172–20–62–134.ec2.internal Ready master 1d v1.11.6</pre><p>We can now proceed to install TraefikEE on this cluster.</p><h3>TraefikEE Installation</h3><p>We expect that the command line traefikeectl command is already installed on your machine. If you haven’t done it yet, check the <a href="https://docs.containo.us/installation-guides/getting-started/#install-traefikeectl">“Install traefikeectl” section of the Installation Guide</a>.</p><pre>$ traefikeectl version<br>Version: v1.0.0-beta17<br>Codename: Gewurztraminer<br>Go version: go1.11.4<br>Built: 2019-01-22_10:12:50AM<br>OS/Arch: darwin/amd64</pre><p>Next step: installation of TraefikEE in one line, using traefikeectl, as covered on <a href="https://blog.containo.us/the-journey-to-traefik-enterprise-edition-product-evaluation-4828508cbc8">the previous blog post</a>.</p><blockquote>Don’t forget it takes some time to download all the required resources</blockquote><pre>$ traefikeectl install \<br>  --licensekey=&quot;$(cat /keybase/…/traefikee-license)&quot; \<br>  --dashboard \<br>  --kubernetes</pre><pre>...</pre><pre>You can access the dashboard with the following credentials:</pre><pre>Username: admin<br>Password: 384bae9a1fe11670</pre><pre>✔ Installation successful</pre><blockquote>Don’t forget to write down the password for later.</blockquote><p>Congratulations, your TraefikEE cluster is installed locally! The last step is to check the topology of the TraefikEE cluster:</p><pre>$ traefikeectl list-nodes<br>Name                                 Role<br>----                                 ----<br>data-node-traefikee-data-node-864tl  DATA NODE<br>data-node-traefikee-data-node-jptsq  DATA NODE<br>data-node-traefikee-data-node-rn4x8  DATA NODE<br>traefikee-control-node-1             CONTROL NODE<br>data-node-traefikee-data-node-l6x2s  DATA NODE<br>data-node-traefikee-data-node-wmm6n  DATA NODE<br>data-node-traefikee-data-node-h2pgb  DATA NODE<br>traefikee-control-node-2             CONTROL NODE (Current Leader)<br>traefikee-control-node-0             CONTROL NODE</pre><p>As expected we have:</p><ul><li>A <a href="https://docs.containo.us/concepts/#nodes-in-the-data-plane">Control Plane</a> composed of <strong>3</strong> nodes, which is the default</li><li>A <a href="https://docs.containo.us/concepts/#nodes-in-the-data-plane">Data Plane</a> composed of <strong>6</strong> nodes, which is <a href="https://docs.containo.us/references/cli/traefikeectl/#install-install">the default behavior (see the flag “ — datanodes”)</a> . TraefikEE sets up 1 data node per worker node of the Kubernetes cluster. It uses a <a href="https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/">Kubernetes Daemon Set</a> under the hood.</li></ul><h3>Accessing the Web Dashboard</h3><p>On the previous post, we used the kubectl port-forward command to access the dashboard by <a href="https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/">forwarding a port locally</a>.</p><p>As this Kubernetes cluster is available from the outside, we want to use a public hostname to access it instead, so the end users can access your applications from anywhere.</p><p>Using the command line kubectl, fetch the public hostname of the Amazon Elastic Load-Balancer allocated during the installation (column EXTERNAL-IP):</p><pre>$ kubectl get svc -n traefikee traefikee-lb</pre><pre>NAME          TYPE         EXTERNAL-IP<br>traefikee-lb  LoadBalancer a277b89-820.us-east-1.elb.amazonaws.com</pre><p>You can now access the dashboard on the URL http://&lt;EXTERNAL-IP&gt;/dashboard/ .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2cbz72VwNuXO7AS7_Y2rGw.png" /><figcaption>All your nodes are belong to us</figcaption></figure><blockquote><strong>(A voice in the background):</strong> My Kubernetes Cluster does not show any EXTERNAL-IP. How can I reach the dashboard (and applications)?</blockquote><blockquote><strong>Containous:</strong> Most of Kubernetes providers propose out of the box implementation for the <a href="https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer">Service of type “LoadBalancer”</a>. If it is not your case, take a look at <a href="https://metallb.universe.tf/">https://metallb.universe.tf/</a>.</blockquote><h3><strong>Deploy an Application</strong></h3><p>As we did on the previous post, we deploy an application based on <a href="https://github.com/containous/whoami">https://github.com/containous/whoami</a>. The Kubernetes definition of this application is available <a href="https://gist.githubusercontent.com/dduportal/ad5e68ffcd9e39c65bdf4af7224304a0/raw/8b87143b084c612f86d66f587df7c058c7fa1aa0/whoami.yaml">here (YAML)</a>.</p><pre>$ kubectl apply -f <a href="https://gist.githubusercontent.com/dduportal/ad5e68ffcd9e39c65bdf4af7224304a0/raw/0ff70f9ae50d7930a9fa6c06bdc15253c81b8af4/whoami.yaml">https://gist.githubusercontent.com/dduportal/ad5e68ffcd9e39c65bdf4af7224304a0/raw/0ff70f9ae50d7930a9fa6c06bdc15253c81b8af4/whoami.yaml</a></pre><p>The dashboard updates itself once the application is deployed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F3UuOHcxspNyDE198GwS5w.png" /></figure><p>You can now reach the application at the URL http://&lt;EXTERNAL-IP&gt;/whoami :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2FHlGmaI2PLcQv5qA125YQ.png" /></figure><h3>High Availability</h3><p>What happens if one of the 6 worker node goes down by accident or for <a href="https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/">maintenance</a>?</p><ul><li>1 of the 6 data nodes goes down (or is rescheduled). The load balancer forwards the traffic to the 5 remaining nodes: no request are lost!</li><li>If 1 of the control nodes was running on this worker node, the remaining nodes elect a new leader and take care of the configuration, until the node comes up.</li></ul><blockquote><strong>(A voice in the background):</strong> Aren’t the control node part of a Raft cluster? If yes, then what happens if only 2 control nodes are up?</blockquote><blockquote><strong>Containous:</strong> The workload handled by the failed node is distributed to the 2 others, so the cluster does not loose data and continues to work as expected. However if the failed node does not comes back, then you are not tolerant to another failure. You can run a TraefikEE of 5 control nodes to be fault tolerant to 2 failures. You can get more information on the <a href="https://docs.containo.us/concepts">TraefikEE documentation</a> or chek how the Raft consensus work <a href="http://thesecretlivesofdata.com/raft/">here</a>.</blockquote><p>To demonstrate this high-availability behavior, we will:</p><ul><li>Run a load test on the “<em>whoami</em>” application served by TraefikEE</li><li>Restart 1 of the 6 Kubernetes worker node</li><li>Verify that no requests are lost</li><li>Validate that the cluster comes back in an healthy state once the Kubernetes worker node is restarted</li></ul><h3>Load Testing the whoami Application</h3><p>We’ll use “slapper” (<a href="https://github.com/ikruglov/slapper">https://github.com/ikruglov/slapper</a>), a go command line providing a real-time view of the load test in the console.</p><pre># You need go - <a href="https://golang.org/dl/">https://golang.org/dl/</a></pre><pre>$ go get -u github.com/ikruglov/slapper<br>...</pre><pre>$ which slapper<br>&quot;${GOPATH}/bin/slapper&quot;</pre><p>Slapper requires a “<a href="https://github.com/ikruglov/slapper#targets-syntax">target file</a>” which is a text file describing the load-testing scenario. Our load-testing scenario is simple: we want to emit HTTP GET requests to the URL of the <em>whoami</em> application.</p><pre>$ cat whoami.target<br>GET http://a277bd4f21fde11e9b5150ea2ab8b589-823458350.us-east-1.elb.amazonaws.com/whoami</pre><p>Let’s start the load testing for 30s, with 50 requests per seconds, and with an adapted scale (with an example output):</p><pre>$ slapper -targets ./whoami.target -minY 100ms -maxY 800ms -timeout 30s -rate 50</pre><pre>sent: 198    in-flight: 6  rate:   50/50 RPS responses: [200]: 192</pre><pre>100-101 ms: [     0/     0]<br>101-102 ms: [     0/     0]<br>102-103 ms: [     0/     0]<br>103-105 ms: [     0/     0]<br>105-106 ms: [     0/     0]<br>106-108 ms: [    13/     0] **************************<br>108-110 ms: [   112/     0] ************************************<br>110-113 ms: [    40/     0] ****************************************<br>113-115 ms: [    10/     0] ********************<br>115-118 ms: [     3/     0] ******<br>118-121 ms: [     4/     0] ********<br>121-125 ms: [     2/     0] ****<br>125-129 ms: [     0/     0]<br>129-133 ms: [     0/     0]<br>133-138 ms: [     0/     0]<br>138-144 ms: [     0/     0]<br>144-150 ms: [     0/     0]<br>...<br>800+ ms: [     0/     0]</pre><h3>Reboot a Worker Node</h3><p>Using the aws and kubectlcommand lines, we get the EC2 instance ID of a worker node, and restart it:</p><pre># Select one of the 6 Kubernetes nodes<br>$ kubectl get nodes<br>NAME STATUS ROLES AGE VERSION<br>...<br>ip-172–20–38–193.ec2.internal Ready node 1d v1.11.6<br>...</pre><pre># Get the EC2 instance ID<br>$ aws ec2 describe-instances --filters &quot;Name=private-dns-name,Values=ip-172-20-38-193.ec2.internal&quot; | grep InstanceId</pre><pre>&quot;InstanceId&quot;: &quot;i-0fdc6a4f95908a2ba&quot;,</pre><pre># Restart the instance<br>$ aws ec2 reboot-instances --instance-ids=i-0fdc6a4f95908a2ba</pre><p>The Dashboard immediately reports that a control node and a data node are unhealthy ( traefikee-control-node-0 and data-node-traefikee-wmm6n in this case):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9QLIL4SMYk8cqyNN47cE0A.png" /></figure><h3>Validate High Availability</h3><p>If you check back the load testing, you can see that no requests have been lost or in error. You might see, however, a punctual growth on the response time (+- 100ms):</p><pre>sent: 25736  in-flight: 2 rate:   50/50 RPS responses: [200]: 25734</pre><p>As soon as the EC2 instance has restarted, all the failed nodes (Kubernetes and TraefikEE) are going back online:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2cbz72VwNuXO7AS7_Y2rGw.png" /><figcaption>TraefikEE cluster back to nominal state</figcaption></figure><p>Check this video of a the load test running with a worker node randomly killed:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FghYsR5CuNiQ%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DghYsR5CuNiQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FghYsR5CuNiQ%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/4e1b77d326bdf9419e0feefe80276253/href">https://medium.com/media/4e1b77d326bdf9419e0feefe80276253/href</a></iframe><p>That’s all for today! We demonstrated the high availability feature of TraefikEE. Oh, and don’t forget to clean your cluster:</p><pre>kops delete cluster --name=&quot;${NAME}&quot;</pre><p>On the next post “The Journey to Traefik Enterprise Edition: HTTPS for everyone”, we’ll focus on how to use TraefikEE with Let’s Encrypt to get HTTPS by default.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7421718be2d8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/containous/the-journey-to-traefik-enterprise-edition-high-availability-7421718be2d8">The Journey to Traefik Enterprise Edition: High Availability</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[The Journey to Traefik Enterprise Edition: Product Evaluation]]></title>
            <link>https://medium.com/containous/the-journey-to-traefik-enterprise-edition-product-evaluation-4828508cbc8?source=rss-db88f00123cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/4828508cbc8</guid>
            <category><![CDATA[traefikee]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[traefik]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Damien Duportal]]></dc:creator>
            <pubDate>Tue, 22 Jan 2019 12:31:00 GMT</pubDate>
            <atom:updated>2019-01-22T13:44:02.935Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NVT4QzvJsw0TTUKSWNwniQ.png" /></figure><p>Welcome to the second post of our journey towards <a href="https://containo.us/traefikee">Traefik Enterprise Edition</a> .</p><p>After our first step (<a href="https://blog.containo.us/the-journey-to-traefik-enterprise-edition-join-the-early-access-program-b73e07d62f30"><em>Join the“Early Access” Program</em></a>), let’s continue by doing a quick evaluation the product on your local machine.</p><blockquote><strong>(A voice in the background):</strong> But, the shiny website says that it is a <strong>distributed</strong> version. How can we assess this on a single machine?</blockquote><blockquote><strong>(Another voice in the background):</strong> A developer machine is <strong>not</strong> a production environment!</blockquote><blockquote><strong>Containous:</strong> These assertions are 100% right dear users! Following the core principles of Traefik, we want to keep things simple and start by getting TraefikEE up and running on a “testing system”. Don’t worry: next steps of the journey are coming, to cover other topics from high availability, to installation on production systems.</blockquote><h3>TraefikEE Installation</h3><p>The next step of the journey is to install TraefikEE: Let’s follow the provided <a href="https://docs.containo.us/">documentation</a>!</p><p><strong><em>“TraefikEE-Cuddle”</em></strong></p><p>The “<a href="https://docs.containo.us/installation-guides/getting-started/">Getting Started with Installation</a>” page recommends to use the command line traefikeectl and guides you on installing this command:</p><pre>$ curl -sSL -o /usr/local/bin/traefikeectl <a href="https://get-the-link-for-your-opeartin-system/traefikeectl">https://get-the-link-for-your-operating-system/traefikeectl</a></pre><pre>$ shasum -a256 /usr/local/bin/traefikeectl # Check against the <a href="https://s3.amazonaws.com/traefikee/binaries/v1.0.0-beta13/SHA256SUMS.txt">SHA256 checksums for your release</a></pre><pre>$ chmod a+x /usr/local/bin/traefikeectl # Make it executable</pre><pre>$ traefikeectl version<br>Version:      v1.0.0-beta16<br>Codename:     Gewurztraminer<br>Go version:   go1.11.4<br>Built:        2019-01-21_06:00:54PM<br>OS/Arch:      darwin/amd64</pre><p><strong><em>Kubernetes Time!</em></strong></p><p>TraefikEE can be installed on different platforms but, this example uses <a href="https://kubernetes.io/">Kubernetes</a>.</p><blockquote><strong>(A voice in the background):</strong> I don’t know Kubernetes<br><strong>Containous:</strong> You don’t have to for this evaluation. But you can learn it from <a href="https://kubernetes.io/docs/tutorials/kubernetes-basics/">https://kubernetes.io/docs/tutorials/kubernetes-basics/</a> and <a href="https://katacoda.com/courses/kubernetes">https://katacoda.com/courses/kubernetes</a></blockquote><p>A Kubernetes installation is required. Don’t worry, we are not <a href="https://en.wiktionary.org/wiki/yak_shaving">yak shaving</a> to select where and how install Kubernetes.</p><p>Instead we’ll use the awesome <a href="https://github.com/kubernetes-sigs/kind">“KinD” (Kubernetes inside Docker)</a> tool providing a disposable Kubernetes locally.</p><blockquote>(From <a href="https://github.com/kubernetes-sigs/kind">https://github.com/kubernetes-sigs/kind</a>)</blockquote><blockquote><em>kind</em> is a tool for running local Kubernetes clusters using Docker container &quot;nodes&quot;.<br><em>kind</em> is primarily designed for testing Kubernetes 1.11+, initially targeting the <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/conformance-tests.md">conformance tests</a>.</blockquote><blockquote>If you have <a href="https://golang.org/">Go</a> and <a href="https://www.docker.com/">Docker</a> installed <em>go get sigs.k8s.io/kind &amp;&amp; kind create cluster</em> is all you need</blockquote><p>Install your Kubernetes cluster for the evaluation:</p><pre>$ kind create cluster --name=traefikee<br>Creating cluster &#39;kind-traefikee&#39; ...<br>✓ Ensuring node image (kindest/node:v1.12.3) 🖼<br>✓ [kind-traefikee-control-plane] Creating node container 📦<br>✓ [kind-traefikee-control-plane] Fixing mounts 🗻<br>✓ [kind-traefikee-control-plane] Starting systemd 🖥<br>✓ [kind-traefikee-control-plane] Waiting for docker to be ready 🐋<br>✓ [kind-traefikee-control-plane] Starting Kubernetes (this may take a minute) ☸</pre><pre>Cluster creation complete. You can now use the cluster with:<br>export KUBECONFIG=&quot;$(kind get kubeconfig-path --name=&quot;traefikee&quot;)&quot;<br>kubectl cluster-info</pre><pre>$ export KUBECONFIG=&quot;$(kind get kubeconfig-path --name=&quot;traefikee&quot;)&quot;</pre><pre>$ kubectl cluster-info<br>Kubernetes master is running at <a href="https://localhost:55243/">https://localhost:55243</a></pre><pre># We have a Kubernetes cluster ready to use!</pre><blockquote>Please note that any local Kubernetes installation passing the <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/conformance-tests.md">conformance tests</a> can be used for the evaluation (as Docker4Mac or Docker4Windows).</blockquote><p><strong><em>TrafikEE Installation</em></strong></p><p>Following the <a href="https://docs.containo.us/installation-guides/kubernetes/oneline/#one-line-installation">official documentation</a>, you may install TraefikEE in one line, using traefikeectl . It might take a few minute to download all the required resources:</p><pre>$ traefikeectl install \<br>  --licensekey=&quot;$(cat /keybase/.../traefikee-license)&quot; \<br>  --dashboard \<br>  --kubernetes<br>...</pre><pre>You can access the dashboard with the following credentials:</pre><pre>Username: admin<br>Password: 4087abf2354666d9</pre><pre>✔ Installation successful</pre><p>Congratulations, your TraefikEE cluster is installed locally!</p><h3>A Tour of TrafikEE</h3><p>TraefikEE is installed, now what?</p><p>First, we have to open access from your web-browser to the cluster:</p><pre># Forward TraefikEE data plane&#39;s port 80 to your localhost:8000<br>kubectl port-forward -n traefikee &quot;$(kubectl get pod -n traefikee | awk &#39;{print $1}&#39; | grep data-node)&quot; 8000:80 &amp;</pre><p>TraefikEE is now exposed on your machine on the following URL: <a href="http://localhost:8000/">http://localhost:8000</a> .</p><blockquote>On a production-grade Kubernetes installation, you would use your external Load Balancer’s public hostname and port.</blockquote><p><strong><em>Web Dashboard</em></strong></p><p>Let’s start the tour with the Web Dashboard, which is enabled because we used the flag--dashboard during the installation.</p><p>Open the URL <a href="http://localhost:8000/">http://localhost:8000</a> and authenticate with the username and password credentials from the traefikeectl install command’s output from earlier.</p><blockquote>In this example, the username is <em>admin</em> and the password is <em>d4087abf2354666d9dsds</em>. These credentials are generated automatically during the installation.</blockquote><p>You can see the default section named “Providers” which shows you the TraefikEE’s routing configuration, generated from Kubernetes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*WjwsKMEF0IBcB9QWV0NNmw.png" /><figcaption>Looks like Traefik’s<a href="https://docs.traefik.io/configuration/api/#web-ui"> WebUI</a></figcaption></figure><p>Using the top bar, navigate to the “Metrics” section to get an overview of the incoming request’s metrics.</p><blockquote><strong>(A voice in the background):</strong> Traefik also provides a “Metrics” page, what is the value of this one?<br><strong>Containous:</strong> It’s the same, except that metrics are aggregated from all the data plane’s nodes.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*e4KQi6kEYofCITe_Uys8tA.png" /><figcaption>Look, someone forgot its password and got HTTP/401 responses</figcaption></figure><p>It’s time to get an overview of the cluster. Browse to the “Cluster” section to check that you have a <a href="https://docs.containo.us/glossary/#control-plane">Control Plane</a> of 3 nodes, and a <a href="https://docs.containo.us/glossary/#data-plane">Data Plane</a> of 1 node.</p><blockquote><strong>(A voice in the background):</strong> Wait, isn’t TraefikEE distributed? Why only 1 node in the data plane?<br><strong>Containous:</strong> By default, there is 1 “TraefikEE Data Node” per Kubernetes node. We are using a single-node Kubernetes hence 1 data node. Wait for the next blog to learn more about the distribution.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*dVuGLz6_WY2_Hz8OctDm7Q.png" /><figcaption>It’s a nice cluster that you have there</figcaption></figure><p><strong><em>Operations with traefikeectl</em></strong></p><p>Next step of this tour is the “Smooth Operations” feature. We know that Engineers love automation. So we made a command line, traefikeectlto automate all the operations on your TraefikEE clusters.</p><p>You already tasted traefikeectl. Let’s do another example of operation by listing all the cluster’s nodes with traefikeectl:</p><pre>$ traefikeectl list-nodes<br>...<br>Name                                 Role<br>----                                 ----<br>data-node-traefikee-data-node-5fplw  DATA NODE<br>traefikee-control-node-0             CONTROL NODE (Current Leader)<br>traefikee-control-node-2             CONTROL NODE<br>traefikee-control-node-1             CONTROL NODE</pre><p>The next section shows another example, but you can already check the traefikeectl ‘s <a href="https://docs.containo.us/references/cli/traefikeectl/">Command Line Reference Documentation</a> to learn more about the operations features.</p><p><strong><em>Deploy an application</em></strong></p><p>TraefikEE is an edge router, which main goal is to route incoming request into your applications.</p><blockquote><strong>(A voice in the background):</strong> Did you just say “applications”? But there are no applications deployed into this Kubernetes, only TraefikEE.<br><strong>Containous:</strong> Patience, there is an example below. But let that sink in: Isn’t the Dashboard an application with incoming traffic?</blockquote><p>Let’s deploy an example application, which Kubernetes’ configuration <a href="https://gist.githubusercontent.com/dduportal/ad5e68ffcd9e39c65bdf4af7224304a0/raw/8b87143b084c612f86d66f587df7c058c7fa1aa0/whoami.yaml">can be found here</a>. It’s an HTTP web service, based on <a href="https://github.com/containous/whoami">https://github.com/containous/whoami</a>, which responds an HTML page with the headers of your request.</p><pre>$ kubectl apply -f <a href="https://gist.githubusercontent.com/dduportal/ad5e68ffcd9e39c65bdf4af7224304a0/raw/8b87143b084c612f86d66f587df7c058c7fa1aa0/whoami.yaml">https://gist.githubusercontent.com/dduportal/ad5e68ffcd9e39c65bdf4af7224304a0/raw/8b87143b084c612f86d66f587df7c058c7fa1aa0/whoami.yaml</a></pre><p>Check the dashboard again. After a few seconds, the routing configuration for the application “whoami” is automatically picked by TraefikEE from Kubernetes: a frontend and 2 associated backends (the 2 replicas).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y2aqof03_f8O3X0vDwHoJA.png" /></figure><p>The application is reachable at the URL <a href="http://localhost:8000/whoami">http://localhost:8000/whoami</a>. As the “whoami” application is scaled to 2 instances, try to reload the page multiple time to see the field “Hostname” changing, due to the Load Balancing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/965/1*lyvaVqfLeoVhxYQcPCKoDQ.png" /><figcaption>Such Web, Much Text</figcaption></figure><p>That’s all for today and this first quick tour. On the next post “The Journey to Traefik Enterprise Edition: High Availability”, we’ll cover the distributed features of TraefikEE.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4828508cbc8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/containous/the-journey-to-traefik-enterprise-edition-product-evaluation-4828508cbc8">The Journey to Traefik Enterprise Edition: Product Evaluation</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[The Journey to Traefik Enterprise Edition: Join the Free “Early Access” Program]]></title>
            <link>https://medium.com/containous/the-journey-to-traefik-enterprise-edition-join-the-free-early-access-program-b73e07d62f30?source=rss-db88f00123cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/b73e07d62f30</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[traefik]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[traefikee]]></category>
            <dc:creator><![CDATA[Damien Duportal]]></dc:creator>
            <pubDate>Mon, 14 Jan 2019 12:31:00 GMT</pubDate>
            <atom:updated>2019-01-14T12:31:00.637Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AMCd3dCEjU7J9JbkIZnqow.png" /></figure><p>Welcome to the first post of our journey with <a href="https://containo.us/traefikee">Traefik Enterprise Edition</a>!</p><p>TraefikEE (Enterprise Edition) is available <a href="https://containo.us/traefikee/#traefikeeTryItModal">through a public beta test</a>. This means that you can evaluate it for free, with an unlimited number of nodes.</p><p>This post guides you through the first steps of your TraefikEE discovery journey: From requesting the “early access” to obtaining your license key and getting started.</p><h3>TraefikEE: Traefik, for the Enterprise World</h3><p>Introduced during KubeCon US 2018 (<a href="https://blog.containo.us/introducing-traefik-enterprise-edition-83b78d09efeb">check out the “Introducing Traefik Enterprise Edition” blog post</a>), TraefikEE is built on top of Traefik and adds clustering features to satisfy the needs of Enterprise customers. All Traefik concepts apply to TraefikEE, so if you already are a Traefik user, you’re in familiar territory.</p><p>TraefikEE runs on the edge of your platform to route the traffic to your applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JYCoTtBKF1Msp5tc.png" /><figcaption>Global Architecture of Traefik Enterprise Edition</figcaption></figure><p>TraefikEE is composed of two planes:</p><ul><li>The <strong>data plane</strong>: horizontally scalable nodes, which forward ingress traffic to your services</li><li>The <strong>control plane</strong>: distributed nodes, implementing <a href="http://thesecretlivesofdata.com/raft/">the raft consensus</a>, which watch your platform and its services, stores topology changes, and reconfigure the data plane to adapt ingress routing dynamically</li></ul><p>This distributed architecture is the cornerstone of TraefikEE’s strengths: natively <strong>highly available</strong>, <strong>scalable</strong>, and <strong>secure</strong>.</p><h3>Support Account and License</h3><p>The journey begins by visiting the TraefikEE website at <a href="https://containo.us/traefikee/">https://containo.us/traefikee</a>, and opting in to the program by clicking the “Early Access” button, and filling the “Get My Key” form.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/493/1*6Pa5Mg1Wg_1tzVh8JYSG5A.png" /><figcaption>If you are not a robot, fill the form</figcaption></figure><blockquote><strong>(A voice in the background):</strong> I’ve been told it is free. Why should I give you my personal information?</blockquote><blockquote><strong>Containous:</strong> We need a way to communicate together, so the form creates a “Support Account” for you in our ticketing system. So you can raise requests if you get any issue with TraefikEE, and we can send you information about update.</blockquote><p>Once you’ve filled out the form, look for a “Welcome to Containous” e-mail sent from <a href="/service/mailto:support@containous.zendesk.com">support@containous.zendesk.com</a> in your mail’s inbox (or, possibly junk folder). Click on the link it contains to validate your account. You will be prompted to set a (strong) password: <a href="https://xkcd.com/936/">you know the story</a>.</p><p>Once your account is validated with a (strong) password, the system will generate a TraefikEE license and send you an e-mail entitled “Your license key” (it may take a couple minutes) which will contain instructions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/670/1*G70HUOi7haoPv44Z1ZCTfg.png" /><figcaption>Knock, knock, you got an email!</figcaption></figure><blockquote><strong>(A voice in the background):</strong> I never received the email. It’s probably tagged as spam by my organization’s mail system.</blockquote><blockquote><strong>Containous:</strong> Instead of the email, you can also browse the customer portal at <a href="https://containous.zendesk.com/hc/en-us">https://containous.zendesk.com/hc/en-us</a> , select the button “Check my existing requests / License” and open the request named “Your license key”.</blockquote><p>Get your license and put it somewhere “secure” (e.g. an encrypted system). For this post series, we store the license in a file, encrypted into a <a href="https://keybase.io/">Keybase.io</a> volume:</p><pre>$ cat /keybase/private/dduportal/traefikee-license<br>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</pre><p>That’s all folks, you can <a href="https://docs.containo.us/installation-guides/getting-started/">get started with the installation from the documentation</a>.</p><p>On the next post “The Journey to Traefik Enterprise Edition: Product Evaluation”, we will install TraefikEE on your machine and take a tour of its features.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b73e07d62f30" width="1" height="1" alt=""><hr><p><a href="https://medium.com/containous/the-journey-to-traefik-enterprise-edition-join-the-free-early-access-program-b73e07d62f30">The Journey to Traefik Enterprise Edition: Join the Free “Early Access” Program</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>