My Blog

PODs are the smallest unit that can be created and deployed within Kubernetes. They will often contain a single container but it is possible to have multiple closely coupled ones. Containers within a POD share a common IP address which means they need to

Secrets are used in a similar way to ConfigMaps but have the advantage of not being stored in clear text. For a reminder of how to use ConfigMaps click here We'll start with some existing secrets that were created in a previous exercise where

Secrets are means of storing and managing sensitive information such as passwords, tokens and keys. They are more secure then using ConfigMaps, which store the data in plain text but it should be noted they do not encrypt the data but encode it as

Configmap contents can be imported into a container in a number of ways, which will mostly be related to how the application is written. This post gives a couple of examples of how to make use of ConfigMaps to populate data within a container.

ConfigMaps within Kubernetes are a means of separating configuration data from the running container image. This means that all necessary configuration data can exist outside the application code. They are not really suited to storing confidential data as they are stored in plain text