Configuration as code
Configuration as code is the practice of representing and managing system or application configuration in machine-readable, version-controlled files.
Automating API Delivery
Configuration as code is the management of application configuration through descriptive, version-controlled files.
- How it is used
- Positions version-controlled API gateway configuration as a way to collaborate on deployment settings and avoid configuration drift.
- How deep it goes
- Defines the practice and contrasts declarative setup with imperative scripts, but provides no complete configuration file or command walkthrough.
- Examples
- Identifies OpenAPI vendor extensions, Apigee Edge configuration files, and Kong and Tyk Kubernetes manifests as gateway-specific forms.
- What you can do after
- Operate/configure it by storing declarative API gateway settings in Git and managing changes through Git workflows.
Read how Automating API Delivery explains configuration as code →
Kubernetes for Developers
Configuration as code is a practice of representing system configuration in files that are managed like source code.
- How it is used
- Uses versioned declarative files to manage Kubernetes environments, workloads, and repeatable maintenance operations.
- How deep it goes
- Explains repository organization, review, rollout, reconciliation, and Secrets, with a worked Job manifest rather than exhaustive configuration reference.
- Examples
- Demonstrates staging and production repositories plus a Kubernetes Job that runs python3 add_tasks.py in its own Pod.
- What you can do after
- Apply configuration through Git, code review, deployment pipelines, GitOps reconciliation, and repeatable Kubernetes Jobs.
Read how Kubernetes for Developers explains configuration as code →
Platform Engineering on Kubernetes
Configuration as code is the practice of representing system and application configuration in version-controlled, machine-readable files.
- How it is used
- Uses versioned Kubernetes YAML and Helm packaging to make application deployments repeatable across environments.
- How deep it goes
- Explains topology, container links, environment variables, packaging, versioning, and Helm tuning, but stops before package production.
- Examples
- Uses Kubernetes resources, service environment variables, Helm charts, and local-to-cloud cluster deployment as examples.
- What you can do after
- Operate/configure application instances by versioning Kubernetes resources and tuning Helm templates for target clusters.
Read how Platform Engineering on Kubernetes explains configuration as code →
Related concepts
- versioninguses · The practice of identifying and managing successive revisions of files, data, models, interfaces, or other artifacts so changes can be tracked and earlier states recovered.
- Anthos Config Managementused by · Anthos Config Management is a Google Anthos component for centrally applying policy and configuration to clusters and services.
- code reviewuses · Code review is the systematic examination of source code or proposed changes to identify problems and assess or improve quality.
- repositoryuses · A software repository is an organized storage location or collection of project files and related artifacts, often managed with version history and change tracking.
- GitOpsequivalent to · GitOps is an operational approach that uses version-controlled declarative configuration as the source of truth and automation to apply or reconcile system state.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.