Connecting and Migrating Applications with Consul Service Mesh

Presented at ServiceMeshCon during KubeCon 2019.
GitHub: https://github.com/lkysow/servicemeshcon-demo
Video: https://www.youtube.com/watch?v=v-ZYkGYi3jQ

Abstract:
Without question, systems are moving to a highly decoupled distributed approach running on modern schedulers like Kubernetes. There are two challenges which practitioners are often faced with while on this journey. How do you migrate legacy applications safely and without interruption to the new world? Once you have migrated, how do you ensure the connectivity and security of applications, potentially running in multiple Kubernetes clusters?
This talk takes a demo driven approach to how the service mesh can solve both of these problems. You will learn how Consul Service Mesh can help to seamlessly and safely migrate an application from Virtual Machines to Kubernetes. Also, how Consul Service Mesh can help connect and secure heterogeneous applications running in multiple Kubernetes clusters.

Transcript

1. Connecting and Migrating Applications with Consul Service Mesh Luke Kysow @lkysow Consul Engineer at HashiCorp Copyright © 2019 HashiCorp
4. Secure By Default All traffic is mTLS encrypted / SPIFFE identity Multi Platform Connect Kube clusters, VMs, bare metal Layer 7 Traffic Management Control traffic via config Consul Service Mesh
5. Service Migration VMs <San Diego> AKS <Los Angeles> chargers NFL
6. Service Migration VMs <San Diego> AKS <Los Angeles> NFL chargers
7. Service Migration Step 1 - Deploy to Kubernetes VMs <San Diego> AKS <Los Angeles> NFL chargers chargers
8. VMs <San Diego> AKS <Los Angeles> NFL chargers chargers Service Migration Step 2 - Test that routing works $ curl -H \ "X-datacenter: kubernetes"
9. VMs <San Diego> AKS <Los Angeles> NFL chargers chargers Service Migration Step 3 - Split traffic 50% 50%
10. VMs <San Diego> AKS <Los Angeles> NFL chargers chargers Service Migration Step 4 - Fully switch over 0% 100%
11. Demo Time!
12. Architecture VMs <San Diego> AKS <Los Angeles> NFL chargers
13. Architecture VMs <San Diego> AKS <Los Angeles> NFL Consul Server Consul Server Federation chargers
14. Architecture VMs <San Diego> AKS <Los Angeles> chargers NFL Consul Server Consul Server Federation Mesh Gateway Mesh Gateway
15. Architecture VMs <San Diego> AKS <Los Angeles> chargers NFL Consul Server Consul Server Federation Mesh Gateway Mesh Gateway sidecar sidecar
16. Architecture VMs <San Diego> AKS <Los Angeles> chargers NFL Consul Server Consul Server Federation Mesh Gateway Mesh Gateway $ curl \ localhost:1234
17. Architecture VMs <San Diego> AKS <Los Angeles> chargers NFL Consul Server Consul Server Federation Mesh Gateway Mesh Gateway
18. Architecture VMs <San Diego> AKS <Los Angeles> chargers NFL Consul Server Consul Server Federation Mesh Gateway Mesh Gateway
19. Architecture VMs <San Diego> AKS <Los Angeles> chargers NFL Consul Server Consul Server Federation Mesh Gateway Mesh Gateway
20. Architecture VMs <San Diego> AKS <Los Angeles> chargers NFL Consul Server Consul Server Federation Mesh Gateway Mesh Gateway
21. ✅
22. ?
23. Helm Install TERMINAL $ kubectl config use-context london $ helm install ./consul-helm --name=consul
24. Installation $ helm install --name consul Observability Integration with Prometheus, Datadog, etc. Intentions $ consul intention create -allow nfl chargers External Certificate Authorities E.g. HashiCorp Vault, AWS PCA Not Covered
25. Thank You! @lkysow 25