Kubernetes Core Concepts: Part 4 - Additional Application Features

Applications have various complexity and typically when first learning and using Kubernetes simple applications like web servers are deployed and used. Applications that need persistent storage and are configured differently per environment have additional requirements. In this course we cover the features of Kubernetes that satisfy these requirements.

Requesting storage for a deployed application in Kubernetes is done in a self-service manner by the application engineer. In this lesson we explain the design rationale for the storage model in Kubernetes and how to use it for your applications that require it.

The previously deployed application is made up of two components (front-end and back-end). The back-end has been using ephemeral storage up until this point. In this lab you’ll enhance the deployment of the backend component to use persistent storage.

Applications need configuration and often it is unique depending upon the environment or platform of where it is running. In this lesson you’ll learn the various approaches Kubernetes has for injecting application configuration at runtime, and compare and contrast each.

Applications need configuration and often it is unique depending upon the environment or platform of where it is running. In this lesson you’ll learn the various approaches Kubernetes has for injecting application configuration at runtime, and compare and contrast each.