Workloads in Kubernetes A workload is an application running on Kubernetes inside a set of pods. A Pod represents a set of running containers on your cluster. * Pods have a defined lifecycle. If a pod fails, you would need to create a new Pod to recover. * To manage pods, you
Volumes in Kubernetes Kubernetes supports several types of volumes, including: Deprecated Volumes * awsElasticBlockStore * azureDisk * azureFile * gcePersistentDisk Migrating Volumes * AWS EBS, Azure Disk, and Azure File have respective CSI migration paths. Other Volume Types * cephfs * cinder * OpenStack has a CSI migration path. ConfigMap * Injects configuration data into pods. * You must create
Containers * Containers are repeatable, which ensures the same behavior wherever they're run due to standardization and included dependencies. * Containers decouple applications from the underlying host infrastructure, making deployment easier across different cloud or OS environments. * Containers form the Pods assigned to a node in a Kubernetes cluster, and they are
Communication between Nodes and the Control Plane * Kubernetes follows a "hub-and-spoke" API pattern where all API usage from nodes (or the pods they run) terminates at the API server. The API server is designed to listen for remote connections on a secure HTTPS port (typically 443) with client authentication and
Welcome to the first lesson! Before we dive straight into Kubernetes, I would like to talk to you about Containers and why they have become central to our deployment paradigms in recent years. It is essential that we understand what containers are in order to see the true value of