Once you've packaged and deployed your application services to a Kubernetes cluster, you have to figure out how to expose them for client access. This course will set you in the right direction for managing ingress traffic to your deployed services.
Once all the hard work of packaging your services into the container format is complete, and you've successfully deployed them to a Kubernetes cluster, you still have the task of exposing those services beyond the cluster for external consumption. In this course, Managing Ingress Traffic Patterns for Kubernetes Services, you'll learn how to expose your Kubernetes services to fit your own unique deployment requirements. First, you'll learn about the different options available for exposing Kubernetes services, and how they might suit particular circumstances. Next, you'll see how to use the Kubernetes Ingress API for managing external traffic as it enters the cluster, and how it can be securely routed to its intended destination. Finally, you'll discover how to accommodate some advanced traffic routing patterns, as well as gain an understanding of some of the future directions for managing ingress in Kubernetes clusters. By the end of the course, you'll have the skills and knowledge necessary for making your microservices available for consumption beyond the Kubernetes cluster boundary.
Nigel is an IT professional with over 25 years of experience, gained in technical and management roles, including as CEO of a technical consulting organization. He has recently returned to his technical roots, and provide tuition in the domain of microservices and container technologies.
Course Overview Hi everyone. My name is Nigel Brown, and welcome to my course, Managing Ingress Traffic Patterns for Kubernetes Services. I'm an independent writer, courseware developer, and a classroom trainer for cloud native software technologies, such as Docker and Kubernetes. Kubernetes has won out as the defacto delivery platform for hosting and orchestrating cloud native software applications that conforms the microservices architecture platform. It's a complex platform with many important features, but one essential ingredient that Kubernetes is required to provide is the reliable and secure routing of external client traffic to its intended destination in the platform. This course deals with the different tools and techniques for managing ingress traffic as it arrives at the edge of a Kubernetes cluster. During the course, the main topics that we'll cover include getting to grips with the Kubernetes ingress concept and ingress controllers, configuring ingress definitions for routing traffic to services in the cluster, automating the secure configuration of transport layer security for deployed services, handling more advanced traffic routing requirements such as canary deployments, and discussing some of the limitations of the ingress API, and using alternative tools and techniques. When we get to the end of the course, you'll have the knowledge of the tools, techniques, and patterns that will enable you to confidently configure traffic routes to the services running in your Kubernetes cluster. Ideally, before you get started with this course, you should already have some practical experience of the Linux command line, some understanding of microservices and their delivery as prepackaged containers, and familiarity with Kubernetes and its APIs. I hope you'll join me on this journey to learn about managing ingress traffic patterns for Kubernetes services.