Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
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
50 Kubernetes Concepts Every DevOps Engineer Should Know

You're reading from   50 Kubernetes Concepts Every DevOps Engineer Should Know Your go-to guide for making production-level decisions on how and why to implement Kubernetes

Arrow left icon
Product type Paperback
Published in Jan 2023
Publisher Packt
ISBN-13 9781804611470
Length 278 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Michael Levan Michael Levan
Author Profile Icon Michael Levan
Michael Levan
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Part 1: First 20 Kubernetes Concepts – In and Out of the Cloud
2. Chapter 1: Kubernetes in Today’s World FREE CHAPTER 3. Chapter 2: Getting the Ball Rolling with Kubernetes and the Top Three Cloud Platforms 4. Chapter 3: Running Kubernetes with Other Cloud Pals 5. Chapter 4: The On-Prem Kubernetes Reality Check 6. Part 2: Next 15 Kubernetes Concepts – Application Strategy and Deployments
7. Chapter 5: Deploying Kubernetes Apps Like a True Cloud Native 8. Chapter 6: Kubernetes Deployment– Same Game, Next Level 9. Part 3: Final 15 Kubernetes Concepts – Security and Monitoring
10. Chapter 7: Kubernetes Monitoring and Observability 11. Chapter 8: Security Reality Check 12. Index 13. Other Books You May Enjoy

Kubernetes Monitoring and Observability

Monitoring and observability for both Ops and Dev teams have always been crucial. Ops teams used to be focused on infrastructure health (virtual machines, bare-metal, networks, storage, and so on) and Devs used to be focused on application health. With Kubernetes, those lines are blurred. In a standard data center environment, it’s easy to split who’s conducting monitoring and observability in a very traditional sense. Kubernetes blends those lines because, for example, Pods are, in a sense, infrastructure pieces because they have to scale and are sort of virtual machines in the traditional sense. They are what holds the application. However, the application is running in a Pod, so if you’re monitoring a Pod, you’re automatically monitoring the containers that are running inside of the Pod.

Because these lines are blurred, both teams are doing both parts of the monitoring process. On a platform engineering or DevOps...

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
Banner background image