Book Image

50 Kubernetes Concepts Every DevOps Engineer Should Know

By : Michael Levan
5 (1)
Book Image

50 Kubernetes Concepts Every DevOps Engineer Should Know

5 (1)
By: Michael Levan

Overview of this book

Kubernetes is a trending topic among engineers, CTOs, CIOs, and other technically sound professionals. Due to its proliferation and importance for all cloud technologies, DevOps engineers nowadays need a solid grasp of key Kubernetes concepts to help their organization thrive. This book equips you with all the requisite information about how Kubernetes works and how to use it for the best results. You’ll learn everything from why cloud native is important to implementing Kubernetes clusters to deploying applications in production. This book takes you on a learning journey, starting from what cloud native is and how to get started with Kubernetes in the cloud, on-premises, and PaaS environments such as OpenShift. Next, you’ll learn about deploying applications in many ways, including Deployment specs, Ingress Specs, and StatefulSet specs. Finally, you’ll be comfortable working with Kubernetes monitoring, observability, and security. Each chapter of 50 Kubernetes Concepts Every DevOps Engineer Should Know is built upon the previous chapter, ensuring that you develop practical skills as you work through the code examples in GitHub, allowing you to follow along while giving you practical knowledge. By the end of this book, you’ll be able to implement Kubernetes in any environment, whether it’s an existing environment, a greenfield environment, or your very own lab running in the cloud or your home.
Table of Contents (14 chapters)
1
Part 1: First 20 Kubernetes Concepts – In and Out of the Cloud
6
Part 2: Next 15 Kubernetes Concepts – Application Strategy and Deployments
9
Part 3: Final 15 Kubernetes Concepts – Security and Monitoring

Understanding cloud-native apps

Although the whole cloud-native thing can feel a bit buzzword-ish in today’s world, there is some merit behind the idea of building cloud-native apps. The way an application is architected matters as it relates to how it can be deployed, managed, and maintained later. The way a platform is built matters because that’s the starting point for how an application can be deployed and how it can be run.

Throughout the years of technology’s existence, there have been multiple different methodologies around how applications are architected and built. The original methods were formed around on-premises systems, such as mainframes and servers. After that, applications started to be architected for virtualized hardware platforms, such as ESXi, and other virtualization products, with the idea in mind of utilizing more of the server, but for different workloads instead of just one workload running like in the bare-metal days. After virtualization...