What's Next?

Recap what we have learned so far and what we are going to learn next.

We'll cover the following

Summary#

With the exception of emptyDir, our choice of Volume type demonstrated in this chapter was not simply based on the ability to use them in a Minikube cluster. Each of these three Volume types will be an essential piece in the chapters that follow.

  • We’ll use hostPath to access Docker server from inside containers.

  • The gitRepo Volume type will be very significant once we start designing a continuous deployment pipeline.

  • The emptyDir type will be required as long as we’re using Minikube. Until we have a better solution for creating a Kubernetes cluster, emptyDir will continue to be used in our Minikube examples.

We have only scratched the surface with Volumes. There are at least two more that we should explore inside Minikube, and one when we change to a different solution for creating a cluster.

The Volumes that we’ll explore throughout the rest of the course are long enough subjects to deserve a separate chapter or, as we already mentioned, require that we get rid of Minikube.

ℹ️ If you’d like to know more about Volumes, please explore Volume v1 core API documentation.

Components explored so far
Components explored so far

The above illustration shows and defines the Kubernetes components explored so far.

Quick Quiz!
Getting Started with ConfigMaps
Mark as Completed
Report an Issue