Historically, application configuration has been managed internal to an application deployment, in environment variables, or in files placed in the filesystem of the running application. As applications evolved into microservices, however, that approach become inadequate. Centralized configuration, including application-specific and shared configuration, versioning and rollback capabilities, and auditing became necessary. As more applications and microservices are becoming containerized and deployed in Kubernetes, configuration continues to be challenging. While Kubernetes offers configuration via ConfigMaps and Secrets, there’s no clear way to manage the properties going into those resources. In this Tanzu Tuesday session, we’ll explore the Tanzu Configuration Service, a means of managing configuration in a Kubernetes-native way using ConfigMaps, but that also offers the benefits afforded in a centralized configuration option.

Craig Walls is a software engineer with VMware and is the author of Spring in Action, Spring Boot in Action, and Build Talking Apps. He’s a zealous promoter of the Spring Framework, speaking frequently at local user groups and conferences and writing about Spring. When he’s not slinging code, Craig is planning his next trip to Disney World or Disneyland and spending as much time as he can with his wife, two daughters, 1 bird and 3 dogs.