Chapter 12. First-class configuration abstractions

 

This chapter covers

  • The problems configuration and secrets solve and the forms those solutions take
  • Modeling and solving configuration problems for Docker services
  • The challenge of delivering secrets to applications
  • Modeling and delivering secrets to Docker services
  • Approaches for using configurations and secrets in Docker services

Applications often run in multiple environments and must adapt to different conditions in those environments. You may run an application locally, in a test environment integrated with collaborating applications and data sources, and finally in production. Perhaps you deploy an application instance for each customer in order to isolate or specialize each customer’s experience from that of others. The adaptations and specializations for each deployment are usually expressed via configuration. Configuration is data interpreted by an application to adapt its behavior to support a use case.

Common examples of configuration data include the following:

  • Features to enable or disable
  • Locations of services the application depends on
  • Limits for internal application resources and activities such as database connection pool sizes and connection time-outs

12.1. Configuration distribution and management

12.2. Separating application and configuration

12.3. Secrets—A special kind of configuration

Summary

sitemap