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

Exploring segregation and namespaces

Once applications are deployed, engineers wipe the sweat off their foreheads, give high fives to their team, and rejoice in their victory. However, what comes after the deployment? Better yet, what if you have to deploy the applications again? Or other types of applications? Or to a different location or segregation point? (Segregation will be discussed later in this chapter.) Getting an application up and running is a mental workout in itself, but the what-comes-next questions you ask yourself are typically the most important. These are things such as the following:

  • Will the next deployment be automated and repeatable?
  • If you have to deploy the application again, will it be an effective deployment?
  • Can (or should) the apps run right next to each other?
  • Which engineers should have access to what apps and why?

Deploying an application is a great victory but designing how and where an application should run is the difference...

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