Book Image

Cloud Native with Kubernetes

By : Alexander Raul
Book Image

Cloud Native with Kubernetes

By: Alexander Raul

Overview of this book

Kubernetes is a modern cloud native container orchestration tool and one of the most popular open source projects worldwide. In addition to the technology being powerful and highly flexible, Kubernetes engineers are in high demand across the industry. This book is a comprehensive guide to deploying, securing, and operating modern cloud native applications on Kubernetes. From the fundamentals to Kubernetes best practices, the book covers essential aspects of configuring applications. You’ll even explore real-world techniques for running clusters in production, tips for setting up observability for cluster resources, and valuable troubleshooting techniques. Finally, you’ll learn how to extend and customize Kubernetes, as well as gaining tips for deploying service meshes, serverless tooling, and more on your cluster. By the end of this Kubernetes book, you’ll be equipped with the tools you need to confidently run and extend modern applications on Kubernetes.
Table of Contents (22 chapters)
1
Section 1: Setting Up Kubernetes
5
Section 2: Configuring and Deploying Applications on Kubernetes
11
Section 3: Running Kubernetes in Production
16
Section 4: Extending Kubernetes

Chapter 7 – Storage on Kubernetes

  1. Volumes are tied to the life cycle of a Pod and are deleted when the Pod is deleted. Persistent Volumes will remain until a cluster is deleted, or they are specifically deleted themselves.
  2. StorageClasses define the type of a Persistent Volume. They can be used to distinguish between different types of storage, such as between faster SSD storage and slower hard drives – or different types of cloud storage. StorageClasses determine where a PersistentVolumeClaim and Persistent Volume will go to get provisioned storage.
  3. Use a managed Kubernetes service with integrated storage provisioning or add a cloud-controller-manager configuration to your cluster.
  4. Any application that needs to store state for longer than the life of an individual Pod would not work with Volumes. Any application that needs to have state that is tolerant to Pod failure needs a Persistent Volume.