Infrastructure as Code (IaC)

Go up to Terms and Definitions

Infrastructure as Code (IaC) represents infrastructure through machine-processable definitions that automated tools use to provision, configure, modify, verify, and remove infrastructure resources.

IaC applies software-engineering and Configuration Management practices to infrastructure. These practices may include source control, review, testing, Version Pinning, automated execution, Traceability, and controlled change.

An IaC definition may describe compute, storage, networking, identity, security, monitoring, provider configuration, relationships, and lifecycle behavior.

Within Crucible, an Infrastructure Baseline may contain IaC definitions that a deployment process realizes through the selected Provider Plugin and Deployment Platform.

representation of infrastructure through machine-processable definitions used by automated tools to provision, configure, modify, verify, and remove infrastructure resources

Generalized from infrastructure automation, software configuration management, cloud computing, and DevOps usage and specialized for the Crucible architecture and operational model.

IaC identifies an engineering approach rather than a particular language, tool, provider, or file format.

Machine-processable infrastructure definitions do not become controlled IaC solely because they exist as files. Effective IaC also depends on version control, review, validation, repeatable execution, and change governance.

An IaC definition specifies the compute nodes, virtual networks, subnets, storage, security rules, and load balancer required for a Kubernetes platform. An automated deployment process realizes those resources in the selected Cloud Environment.