Container Orchestration with Traefik 2.x
0 likes145 views
The presentation includes key features of Traefk - a modern reverse proxy and load balancer for micro services that easily integrates with many cluster technology such as Kubernetes and Docker Swarm.
Ad
More Related Content
What's hot (19)
Similar to Container Orchestration with Traefik 2.x (20)
Ad
More from Jakub Hajek (6)
Ad
Recently uploaded (20)
Container Orchestration with Traefik 2.x
- 1. CONTAINER ORCHESTRATION WITH TRAEFIK 2.X JAKUB HAJEK JANUARY 15TH, 2020
- 2. ▸ I am the owner and technical consultant working for Cometari ▸ I’ve been system admin since 1998 ▸ Cometari is a solutions company implementing DevOps culture and providing consultancy, workshops and software services. ▸ Our expertise are DevOps, Elastic Stack - log analysis, Cloud ▸ We are deeply involved in the travel tech industry ▸ However our solutions go much further than just integrating travel API’s. INTRODUCTION
- 3. “I strongly believe that implementing DevOps culture, across the entire organisation, should provide measurable value and solve the real issue rather than generate a new one.” Jakub Hajek, Cometari
- 4. The goal of this presentation is to show you how we work with distributed systems and how Traefik makes our daily work easier.
- 5. CONTAINERS
- 6. IMMUTABLE CONTAINERS ▸ Mutable vs Immutable ▸ No incremental changes to the image ▸ No more drifting configuration ▸ (No) imperative updates ▸ Base image + source code = An artefact / immutable image ▸ The artefact is scaling unit in distributed systems ▸ Canary and mirror deployments ▸ Rollback if an error occurs
- 7. Immutable containers are at the core of any distributed systems
- 8. TRAEFIK 2.X
- 9. TRAEFIK 2.X KEY FEATURES ▸ TCP support ▸ ROUTER= frontend, SERVICE=backend, MIDDLEWARES=rules ▸ Fully customisable routes via middleware, which can be reused on many routers ▸ YAML, TOML is still good ▸ A new dashboard with web UI ▸ Canary deployment with Service Load balancer ▸ Network traffic Mirroring with Service Load balancer ▸ Consul catalog
- 10. ENTRYPOINTS :80, :443 ROUTERS PROVIDER 1 Traefik configuration introduction PROVIDER CONNECTION INFORMATION SERVICES MIDDLEWARES CERTIFICATES PROVIDER 2 DYNAMIC (WHILE RUNNING)STATIC (STARTUP TIME)
- 11. ENTRYPOINT ROUTER SERVICE MIDDLEWARE 1 MIDDLEWARE 2 MIDDLEWARE 3 Request Calls to backend servers Tweaking request before / after the arrives to their destination
- 12. MIRRORING OR LIVE TRAFFIC SHADOW ▸ Understand difference between Deployment vs Release ▸ Deployment brings new code to the production, no production traffic yet! ▸ Run smoke, integration tests to make sure that new deployment has no impact to your users ▸ Release brings live traffic to a deployment. ▸ We can shadow live traffic to the new deployment and reduce the risk of failure.
- 13. MIRRORING VERSION 2 VERSION 1 https://service Mirroring with Service Load Balancer 20% https://github.com/containous/traefik/issues/2989
- 14. CANARY DEPLOYMENT ▸ Deployment vs Release ▸ Instead of switching to new version in one step, we use a phased approach ▸ We deploy a new app in a small part of the production infrastructure ▸ Only a few users (1%) are routed to the newest version (Release) ▸ With no errors reported, the new version can be released to the rest of the infrastructure.
- 15. CANARY VERSION 2 VERSION 1 https://service Canary deployment with Service Load balancers 1% of live traffic, a few users Majority of users https://github.com/containous/traefik/issues/1164
- 16. CANARY VERSION 2 https://service Canary deployment with Service Load balancers VERSION 2VERSION 2VERSION 2
- 17. IMMUTABLE CONTAINER WITH TRAEFIK ▸ Custom image with Traefik with added SSL certificate into image ▸ Configuration files added directly to the image ▸ Works perfectly if you bought SSL cert and don’t use dynamically updated Let’s Encrypt ▸ Horizontal scalability is simple, no need to care about the persistence for Let’s Encrypt certificates
- 18. OBSERVABILITY ▸ Enable Prometheus or any other backend ▸ Use Grafana to visualise metrics ▸ Use existing dashboards to visualise data (or develop your own)
- 19. LOGGING AND VISUALISING ACCESS LOGS ▸ Traefik logs are in JSON including startup and errors events ▸ Access logs are written to STDOUT in JSON format. ▸ Treat logs as an event and transfer them to external system (Elastic Stack + Fluentd) ▸ Use Kibana and Logs tab to have live data streaming ▸ Develop dashboard with a map and place GEO points of IP addresses
- 20. CONFIGURATION TIPS ▸ Don’t mix static configuration vs dynamic configuration ▸ CLI command can be used for static config or if you prefer you can define config file as well ▸ Labels can be used to define dynamic configuration or config files ▸ directory with WATCH flag enabled as well ▸ More advanced rules configuration via middleware are dynamically defined ▸ The most flexible is to run Traefik as container, instead of binary directly from host ▸ Healthcheck for your services are crucial
- 21. DEMO ENVIRONMENT
- 22. DEMO ENVIRONMENT IN DETAILS ▸ Docker Swarm cluster* consisting of 4 nodes ▸ SSL certs issued by Lets Encrypt ▸ FQDN domains: ▸ https://traefik.labs.cometari.eu ▸ https://node-app.labs.cometari.eu ▸ https://canary.labs.cometari.eu ▸ DNS Round Robin: Route 53 with its implemented health checks ▸ Prometheus and Grafana ▸ Elastic stack, Fluentd to store and visualise data logs ▸ Web Server and NodeJS backend ▸ Stacks: Traefik, App stack, Consul for consul catalog
- 23. Diagram of demo environment TRAEFIK WEB FRONTEND NODEJS BACKEND
- 24. Overview of configuration files!
- 25. DEMO TIME
- 26. DEMO SCENARIOS ▸ Web UI to see how services are deployed ▸ Scaling services and generating some network traffic via Slapper ▸ Example of Canary deployment ▸ Metrics from Traefik in open metrics format
- 27. SUMMARY ▸ Traefik provides flexible way to expose services, auto discovery ▸ It can be configured in multiple way, there are no ready to use config - just refer to configuration tips ▸ Fully customise routes via middlewares ▸ Easily integrates with every major cluster technology ▸ Lets Encrypt integrated, managing SSL certs is easy ▸ Metrics, Tracing, Logs ▸ Rolling out releases thanks to Canary deployments ▸ Mirroring - duplicating incoming request and send them to different services.