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)
Part 1: First 20 Kubernetes Concepts – In and Out of the Cloud
Part 2: Next 15 Kubernetes Concepts – Application Strategy and Deployments
Part 3: Final 15 Kubernetes Concepts – Security and Monitoring

Kubernetes Secrets

Wrapping up this chapter, and the overall book, you’ll learn about Kubernetes Secrets.

Secrets, in short, are anything that you don’t want to be in plain text. Typically, they are things such as passwords and API keys. However, they could even be usernames. Any type of data that you don’t want to be in plain text, at rest, or in transit can be considered a Secret.

At this point in your engineering journey, it’s assumed that you don’t need to be taught about Secrets, so we’re going to skip that part and dive right into the hands-on part.

Creating Kubernetes Secrets

To create a Kubernetes Secret, you’ll use the secret resource from the v1 core API group.

For example, the following is a Secret called testsecret with a username and password:

apiVersion: v1
kind: Secret
  name: testsecret
type: Opaque
  username: YWRtaW4=
  password: MWYyZDFlMmU2N2Rm