Book Image

50 Kubernetes Concepts Every DevOps Engineer Should Know

By : Michael Levan
Book Image

50 Kubernetes Concepts Every DevOps Engineer Should Know

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

Out-of-the-box Kubernetes security

At this point in time, there are two typical groups of people—those who are so incredibly new to Kubernetes and those who are as close to an expert as possible.

With the group that’s new to Kubernetes, they’re just trying to understand the breakdown of the environment. They aren’t even at the stage of thinking about security yet.

With the group that’s advanced—yes, they’re implementing security practices. The problem is that the advanced group is extremely small compared to the group that’s new to Kubernetes.

Then, there are the engineers that are somewhat in between. They aren’t super new, but they aren’t ridiculously advanced either. This is the group that a lot of engineers fall into, and quite frankly, the group that’s somewhat in between is just starting to think about security.

As with most platforms, nothing is 100% secure out of the box. In fact, regardless...