Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Introduction to DevOps with Kubernetes

You're reading from   Introduction to DevOps with Kubernetes Build scalable cloud-native applications using DevOps patterns created with Kubernetes

Arrow left icon
Product type Paperback
Published in May 2019
Publisher
ISBN-13 9781789808285
Length 374 pages
Edition 1st Edition
Languages
Arrow right icon
Authors (2):
Arrow left icon
Süleyman Akbaş Süleyman Akbaş
Author Profile Icon Süleyman Akbaş
Süleyman Akbaş
Onur Yılmaz Onur Yılmaz
Author Profile Icon Onur Yılmaz
Onur Yılmaz
Arrow right icon
View More author details
Toc

Table of Contents (11) Chapters Close

Preface 1. Chapter 1: Introduction to DevOps 2. Chapter 2: Introduction to Microservices and Containers FREE CHAPTER 3. Chapter 3: Introduction to Kubernetes 4. Chapter 4: Creating a Kubernetes Cluster 5. Chapter 5: Deploy an Application to Kubernetes 6. Chapter 6: Configuration and Storage Management in Kubernetes 7. Chapter 7: Updating and Scaling an Application in Kubernetes 8. Chapter 8: Troubleshooting Applications in Kubernetes 9. Chapter 9: Monitoring Applications in Kubernetes Appendix

Service Discovery in Kubernetes

Kubernetes manages containerized microservice applications by creating pods. Pods are the building blocks of Kubernetes, where multiple containers are grouped together and share the same network interface. For every pod, Kubernetes assigns an IP that is reachable within the Kubernetes cluster; however, the pods are ephemeral in their nature. In other words, pods and their IPs could change when they are assigned to different nodes. In order to reliably access pods, Kubernetes provides an abstraction layer known as service. Kubernetes services group a logical set of pods that can run on the different nodes inside the cluster and enable other pods to reach them over the service.

Let's imagine having a backend deployment in Kubernetes with two replicas and a frontend deployment with three replicas. To reach the backend pods from the frontend pods, the IPs of the backends should be made available to the frontends, as shown in Figure 5.9. Additionally...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime