From the course: Automating Kubernetes with GitOps

Unlock this course with a free trial

Join today to access over 24,700 courses taught by industry experts.

Providing configuration

Providing configuration - Kubernetes Tutorial

From the course: Automating Kubernetes with GitOps

Start my 1-month free trial Buy for my team

Providing configuration

“

- So before we can talk about the case of the Secret, we need to talk about how to provide configuration. To guarantee flexibility in the GitOps environment, configuration should be stored in external objects. Don't put it in your images or anywhere else, external objects so that you can manage it separately, because that allows you to use different configurations in different GitOps environments while still keeping the same application manifests. ConfigMaps are provided by Kubernetes to store contents in ASCII format and Secrets are provided to store content in Base64 encoded format. ConfigMaps and Secrets are used to store environment variables, startup parameters, configuration files, TLS keys, and other keys as well as passwords. Before I show you in depth what is going on with Secrets and how to deal with Secrets, which is really a specific case, let me quickly remind you how to work with ConfigMaps. I'm assuming that you already are more or less familiar with ConfigMaps. I just…

Contents