This is the fourth part of Kubernetes mini-series Kubernetes explained deep enough For web version of this blog and more information about docker, Kubernetes and Docker Certification, please visit: Part 1: Introduction Part 2: Kubernetes explained deep enough: Storage Part 3: Kubernetes explained deep enough: Deployments Part 4: Kubernetes explained deep enough: Configuration — this blog Visit Kubernetes documentation if you need a refresher about Configuration Basic definitions are provided on diagrams below Kubernetes natively supports 2 resources geared towards storing configuration consumed by pods. Both configuration types required data to be represented in a key:value pair format. Config maps are not suited for storing large quantities of data. Please use external storage for this purpose. As a side-note, etcd, key-value store where Kubernetes stores all its state can only hold resources up to 1MN in size.