Louis Ryan's guest appearances

Louis Ryan

Cloud Engineering Archives - Software Engineering Daily

Kubernetes Podcast from Google

Software Daily

David Aronchick

Idit Levine

Clayton Coleman

Aparna Sinha

Brian Grant

Ville Aikas

Maya Kaczorowski

Yoshi Tamura

Ralph Squillace

Liz Rice

Matt Klein

Alexis Richardson

Grant Miller

Webb Brown

Eric Brewer

OwlTail

Istio 1.2 has been released. Louis Ryan is a core contributor to Istio and a member of its Technical Oversight Committee, in his role as Principal Engineer at Google Cloud. He talks to Craig and Adam about his history with API infrastructure and the service mesh, and the history and future of the Istio project. Do you have something cool to share? Some questions? Let us know:  web: kubernetespodcast.com mail: kubernetespodcast@google.com twitter: @kubernetespod  Chatter of the week  Adam goes to the Northwest Garlic Festival  Anthropomorphic garlic cloves Pineapple Garlic Jelly   Craig goes to Fleetwood Mac  News of the week  Istio 1.2 HAProxy 2.0 New Docker Desktop for Windows with WSL 2 coming Facebook peels the lid off Tupperware Wind River adds Docker and Kubernetes support for the edge Banzai Cloud adds Istio to Pipeline Apple joins the CNCF as a Platinum member Modernize IT 2019 digital conference from Google Cloud  Links from the interview  Istio service mesh Louis Ryan’s talk at QCon gRPC Sidecar pattern Core features of Istio amalgam8 from IBM in 2016 What is a service mesh? Envoy Proxy Istio 1.2 release notes  Snow Leopard: 0 new features The original announcement of Istio 0.1   The upcoming Istio operator Common misconceptions: Design goals Community  Weekly community meeting Working groups discuss.istio.io     Related episodes: SPIFFE, with Andrew Jessup Envoy, with Matt Klein Istio at 1.0, with Dan Ciruli and Jasmine Jaksic   Louis Ryan on Twitter

Istio 1.2 has been released. Louis Ryan is a core contributor to Istio and a member of its Technical Oversight Committee, in his role as Principal Engineer at Google Cloud. He talks to <a href="https://kubernetespodcast.com/about" rel="nofollow" target="_blank">Craig and Adam</a> about his history with API infrastructure and the service mesh, and the history and future of the Istio project. Do you have something cool to share? Some questions? Let us know: <ul> <li>web: <a href="https://kubernetespodcast.com" rel="nofollow" target="_blank">kubernetespodcast.com</a></li> <li>mail: <a href="mailto:kubernetespodcast@google.com">kubernetespodcast@google.com</a></li> <li>twitter: <a href="https://twitter.com/kubernetespod" rel="nofollow" target="_blank">@kubernetespod</a></li> </ul> <h3>Chatter of the week</h3> <ul> <li><a href="https://www.nwgarlicfestival.org/" rel="nofollow" target="_blank">Adam goes to the Northwest Garlic Festival</a> <ul> <li><a href="https://www.facebook.com/columbiablackgarlic/photos/a.1646747472222308/2424648507765530/" rel="nofollow" target="_blank">Anthropomorphic garlic cloves</a></li> <li><a href="http://www.justysjelly.com/jellies/pineapple-roasted-garlic/" rel="nofollow" target="_blank">Pineapple Garlic Jelly</a></li> </ul> </li> <li><a href="https://twitter.com/craigbox/status/1140376418578305028" rel="nofollow" target="_blank">Craig goes to Fleetwood Mac</a></li> </ul> <h3>News of the week</h3> <ul> <li><a href="https://istio.io/blog/2019/announcing-1.2/" rel="nofollow" target="_blank">Istio 1.2</a></li> <li><a href="https://www.haproxy.com/blog/haproxy-2-0-and-beyond/" rel="nofollow" target="_blank">HAProxy 2.0</a></li> <li><a href="https://engineering.docker.com/2019/06/docker-hearts-wsl-2/" rel="nofollow" target="_blank">New Docker Desktop for Windows with WSL 2 coming</a></li> <li><a href="https://code.fb.com/data-center-engineering/tupperware/" rel="nofollow" target="_blank">Facebook peels the lid off Tupperware</a></li> <li><a href="http://linuxgizmos.com/wind-river-linux-adds-docker-and-kubernetes-support-for-the-edge/" rel="nofollow" target="_blank">Wind River adds Docker and Kubernetes support for the edge</a></li> <li><a href="https://banzaicloud.com/blog/istio-the-easy-way/" rel="nofollow" target="_blank">Banzai Cloud adds Istio to Pipeline</a></li> <li><a href="https://www.cncf.io/blog/2019/06/11/apple-joins-cloud-native-computing-foundation-as-platinum-end-user-member/" rel="nofollow" target="_blank">Apple joins the CNCF as a Platinum member</a></li> <li><a href="https://cloudonair.withgoogle.com/events/modernize-it-2019" rel="nofollow" target="_blank">Modernize IT 2019</a> digital conference from Google Cloud</li> </ul> <h3>Links from the interview</h3> <ul> <li><a href="https://istio.io" rel="nofollow" target="_blank">Istio service mesh</a></li> <li><a href="https://www.infoq.com/presentations/istio-service-mesh/" rel="nofollow" target="_blank">Louis Ryan’s talk at QCon</a></li> <li><a href="https://grpc.io" rel="nofollow" target="_blank">gRPC</a></li> <li><a href="https://docs.microsoft.com/en-us/azure/architecture/patterns/sidecar" rel="nofollow" target="_blank">Sidecar pattern</a></li> <li><a href="https://istio.io/docs/concepts/what-is-istio/#core-features" rel="nofollow" target="_blank">Core features of Istio</a></li> <li><a href="https://www.ibm.com/blogs/cloud-archive/2016/06/amalgam8-integration-fabric-microservices-cloud/" rel="nofollow" target="_blank">amalgam8</a> from IBM in 2016</li> <li><a href="https://istio.io/docs/concepts/what-is-istio/#what-is-a-service-mesh" rel="nofollow" target="_blank">What is a service mesh?</a></li> <li><a href="https://www.envoyproxy.io/" rel="nofollow" target="_blank">Envoy Proxy</a></li> <li><a href="https://istio.io/about/notes/1.2/" rel="nofollow" target="_blank">Istio 1.2 release notes</a> <ul> <li><a href="https://512pixels.net/2015/04/the-snow-leopard-moment/" rel="nofollow" target="_blank">Snow Leopard: 0 new features</a></li> <li><a href="https://istio.io/blog/2017/0.1-announcement/" rel="nofollow" target="_blank">The original announcement of Istio 0.1</a></li> </ul> </li> <li><a href="https://github.com/istio/operator" rel="nofollow" target="_blank">The upcoming Istio operator</a></li> <li>Common misconceptions: <ul> <li><a href="https://istio.io/docs/concepts/what-is-istio/#design-goals" rel="nofollow" target="_blank">Design goals</a></li> <li><a href="https://github.com/istio/community" rel="nofollow" target="_blank">Community</a> <ul> <li><a href="https://github.com/istio/community#community-meeting" rel="nofollow" target="_blank">Weekly community meeting</a></li> <li><a href="https://github.com/istio/community/blob/master/WORKING-GROUPS.md" rel="nofollow" target="_blank">Working groups</a></li> <li><a href="https://discuss.istio.io/" rel="nofollow" target="_blank">discuss.istio.io</a></li> </ul> </li> </ul> </li> <li>Related episodes: <ul> <li><a href="https://kubernetespodcast.com/episode/045-spiffe/" rel="nofollow" target="_blank">SPIFFE, with Andrew Jessup</a></li> <li><a href="http://kubernetespodcast.com/episode/033-envoy/" rel="nofollow" target="_blank">Envoy, with Matt Klein</a></li> <li><a href="https://kubernetespodcast.com/episode/015-istio/" rel="nofollow" target="_blank">Istio at 1.0, with Dan Ciruli and Jasmine Jaksic</a></li> </ul> </li> <li><a href="https://twitter.com/louiscryan" rel="nofollow" target="_blank">Louis Ryan on Twitter</a></li></ul>

Istio 1.2, with Louis Ryan

A single user request hits Google’s servers. A user is looking for search results.  In order to deliver those search results, that request will have to hit several different internal services on the way to getting a response.  These different services work together to satisfy the user’s request. All of these services need to communicate efficiently, they need to scale, and they need to be secure. Services need to have a consistent way of being “observable”–allowing logging and monitoring. Services need to have proper security. Since every service wants these different features (like communication, load balancing, security), it makes sense to build these features into a common system that can be deployed to every server. Louis Ryan has spent his years at Google working on service infrastructure. During that time, he has seen massive changes in the way traffic flows through Google. First, the rise of Android, and all of the user traffic from mobile phones. And second, the rise of the Google Cloud Platform, which meant that Google was now responsible for nodes deployed by users outside of Google. These two changes–mobile and cloud–led to an increase in the amount of traffic and the type of traffic. All of this traffic leads to more internal services communicating with each other. How does service networking change in such an environment? Google’s adaptation to the new networking conditions is to introduce a “service mesh”. A service mesh is a network for services. It provides observability, resiliency, traffic control, and other features to every service that plugs into it. Each service needs to plug into the service mesh. In Kubernetes, services connect to the mesh through a sidecar. Let me explain the term “sidecar.” Kubernetes manages its resources in pods, and each pod contains a set of containers. You might have a pod that is dedicated to responding to any user that is requesting a picture of a cat. Within that pod, you not only have the container that serves the cat picture–you also have other “sidecar” containers that help out an application container.  You could have a sidecar that gets deployed next to your application container that handles logging, or a sidecar that helps out with monitoring, or network communications.  If you are using the Istio service mesh, that means that you are using a sidecar called Envoy. Envoy is a sidecar called a “service proxy” that provides configuration updates, load balancing, proxying, and lots of other benefits. If we get all that out of Envoy, why do we need a separate abstraction of a “service mesh”? Because it helps to have a tool that aggregates and centralizes all the different communications among these proxies. Every service gets a sidecar for a service proxy. Every service proxy communicates with the centralized service mesh. Louis Ryan joins this episode to explain the motivations for building the Istio service mesh, and the problems it solves for Kubernetes developers. For the next two weeks, we are covering exclusively the world of Kubernetes. Kubernetes is a project that is likely to have as much impact as Linux–and it is very early days. Whether you are an expert in Kubernetes or you are just starting out, we have lots of episodes to fit your learning curve. To find all of our old episodes about Kubernetes (including a previous show about Istio), download the Software Engineering Daily app for iOS or for Android. In other podcast players, only the most 100 recent episodes are available, but in our apps you can find all 650 episodes–and there is also plenty of content that is totally unrelated to Kubernetes! The post Istio Motivations with Louis Ryan appeared first on Software Engineering Daily.

A single user request hits Google’s servers. A user is looking for search results. In order to deliver those search results, that request will have to hit several different internal services on the way to getting a response. These different services work together to satisfy the user’s request. All of these services need to communicate efficiently, they need to scale, and they need to be secure. Services need to have a consistent way of being “observable”–allowing logging and monitoring. Services need to have proper security. Since every service wants these different features (like communication, load balancing, security), it makes sense to build these features into a common system that can be deployed to every server. Louis Ryan has spent his years at Google working on service infrastructure. During that time, he has seen massive changes in the way traffic flows through Google. First, the rise of Android, and all of the user traffic from mobile phones. And second, the rise of the Google Cloud Platform, which meant that Google was now responsible for nodes deployed by users outside of Google. These two changes–mobile and cloud–led to an increase in the amount of traffic and the type of traffic. All of this traffic leads to more internal services communicating with each other. How does service networking change in such an environment? Google’s adaptation to the new networking conditions is to introduce a “service mesh”. A service mesh is a network for services. It provides observability, resiliency, traffic control, and other features to every service that plugs into it. Each service needs to plug into the service mesh. In Kubernetes, services connect to the mesh through a sidecar. Let me explain the term “sidecar.” Kubernetes manages its resources in pods, and each pod contains a set of containers. You might have a pod that is dedicated to responding to any user that is requesting a picture of a cat. Within that pod, you not only have the container that serves the cat picture–you also have other “sidecar” containers that help out an application container. You could have a sidecar that gets deployed next to your application container that handles logging, or a sidecar that helps out with monitoring, or network communications. If you are using the Istio service mesh, that means that you are using a sidecar called Envoy. Envoy is a sidecar called a “service proxy” that provides configuration updates, load balancing, proxying, and lots of other benefits. If we get all that out of Envoy, why do we need a separate abstraction of a “service mesh”? Because it helps to have a tool that aggregates and centralizes all the different communications among these proxies. Every service gets a sidecar for a service proxy. Every service proxy communicates with the centralized service mesh. Louis Ryan joins this episode to explain the motivations for building the Istio service mesh, and the problems it solves for Kubernetes developers. For the next two weeks, we are covering exclusively the world of Kubernetes. Kubernetes is a project that is likely to have as much impact as Linux–and it is very early days. Whether you are an expert in Kubernetes or you are just starting out, we have lots of episodes to fit your learning curve. To find all of our old episodes about Kubernetes (including a previous show about Istio), download <a href="https://itunes.apple.com/us/app/software-engineering-daily-podcast-app/id1253734426?mt=8" rel="nofollow" target="_blank">the Software Engineering Daily app for iOS</a> or <a href="https://play.google.com/store/apps/details?id=com.koalatea.thehollidayinn.softwareengineeringdaily" rel="nofollow" target="_blank">for Android</a>. In other podcast players, only the most 100 recent episodes are available, but in our apps you can find all 650 episodes–and there is also plenty of content that is totally unrelated to Kubernetes! The post <a href="https://softwareengineeringdaily.com/2018/01/09/istio-motivations-with-louis-ryan/" rel="nofollow" target="_blank">Istio Motivations with Louis Ryan</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Istio Motivations with Louis Ryan

Varun Talwar

Modern software applications are often built out of loosely coupled microservices. These services can be written in different languages, by different people, but communication between services needs to be standardized. For this reason, a service proxy is useful. A service proxy is a sidecar container that sits next to a service and facilitates communications with other services.  Once every service has a sidecar proxy, that sidecar can be used as a way to communicate with a centralized control plane. The sidecar can report telemetry data to the control plane, and the control plane can be used to set policies across services, such as rules for scaling and load balancing which might vary from service to service.  Istio is an open platform to connect, manage, and secure microservices. Istio is a service mesh that uses Envoy service proxies. If all of this sounds confusing–don’t worry, we’ll explain it all in today’s interview with Varun Talwar and Louis Ryan, who work on Istio at Google. Check out our new topic feeds, in iTunes or wherever you find your podcasts. We’ve sorted all 500 of our old episodes into categories like business, blockchain, cloud engineering, JavaScript, machine learning, and greatest hits. Whatever specific area of software you are curious about, we have a feed for you. Check the show notes for more details. The post Istio Service Mesh with Varun Talwar and Louis Ryan appeared first on Software Engineering Daily.

Modern software applications are often built out of loosely coupled microservices. These services can be written in different languages, by different people, but communication between services needs to be standardized. For this reason, a service proxy is useful. A service proxy is a sidecar container that sits next to a service and facilitates communications with other services. Once every service has a sidecar proxy, that sidecar can be used as a way to communicate with a centralized control plane. The sidecar can report telemetry data to the control plane, and the control plane can be used to set policies across services, such as rules for scaling and load balancing which might vary from service to service. Istio is an open platform to connect, manage, and secure microservices. Istio is a service mesh that uses <a href="https://softwareengineeringdaily.com/2017/02/14/service-proxying-with-matt-klein/" rel="nofollow" target="_blank">Envoy service proxies</a>. If all of this sounds confusing–don’t worry, we’ll explain it all in today’s interview with Varun Talwar and Louis Ryan, who work on Istio at Google. Check out our new <a href="https://softwareengineeringdaily.com/2017/05/02/new-topic-feeds/" rel="nofollow" target="_blank">topic feeds</a>, in iTunes or wherever you find your podcasts. We’ve sorted all 500 of our old episodes into categories like <a href="https://itunes.apple.com/us/podcast/sed-business-and-philosophy/id1229506610" rel="nofollow" target="_blank">business</a>, <a href="https://itunes.apple.com/us/podcast/blockchain-software-engineering-daily/id1230807219" rel="nofollow" target="_blank">blockchain</a>, <a href="https://itunes.apple.com/us/podcast/cloud-engineering-software-engineering-daily/id1230806692" rel="nofollow" target="_blank">cloud engineering</a>, <a href="https://itunes.apple.com/us/podcast/javascript-software-engineering-daily/id1232093829" rel="nofollow" target="_blank">JavaScript</a>, <a href="https://itunes.apple.com/us/podcast/machine-learning-software-engineering-daily/id1230807136" rel="nofollow" target="_blank">machine learning</a>, and <a href="https://itunes.apple.com/us/podcast/greatest-hits-software-engineering-daily/id1229486348" rel="nofollow" target="_blank">greatest hits</a>. Whatever specific area of software you are curious about, we have a feed for you. Check the show notes for more details. The post <a href="https://softwareengineeringdaily.com/2017/06/27/istio-service-mesh-with-varun-talwar-and-louis-ryan/" rel="nofollow" target="_blank">Istio Service Mesh with Varun Talwar and Louis Ryan</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Istio Service Mesh with Varun Talwar and Louis Ryan