This title slide is titled "Deferred Infrastructure Creation with CI-Controlled Variables." It offers an overview of a two-phase deployment: infrastructure first, then CI-driven app deployment.

Deferred Infrastructure Creation with CI-Controlled Variables

Overview of two-phase deployment: infra first, then CI-driven app.

Source: Overview of two-phase deployment: infra first, then CI-driven app.

This slide overviews a two-phase deployment pattern. It highlights separation of infrastructure and application deployments to ensure clean, repeatable processes.

Overview

• Two-phase deployment pattern
• Separation of infrastructure and application deployment
• Ensures clean, repeatable deployments

Source: Deferred Infrastructure Creation with CI-Controlled Variables

Phase 1 sets up essential Azure infrastructure once or manually by creating a Resource Group, Virtual Network, Virtual Machine, and Azure Container Registry. It does not create an Azure Container Instance (createaci = false).

Phase 1 – Infrastructure Setup (Manual or Once)

• Creates Resource Group (RG)
• Creates Virtual Network (VNET)
• Creates Virtual Machine (VM)
• Creates Azure Container Registry (ACR)
• Does NOT create ACI (createaci = false)

In Phase 2 (Application Deployment via CI/CD), CI builds a Docker image and pushes it to ACR, while Terraform creates an ACI using Phase 1 infrastructure. This enables a clean, automated rollout.

Phase 2 – Application Deployment (CI/CD)

• CI builds Docker image
• Pushes image to ACR
• Terraform creates ACI
• ACI uses Phase 1 infrastructure
• Enables clean, automated rollout

The workflow starts with a developer committing code, triggering the CI/CD pipeline to build and push a Docker image to ACR. Terraform then deploys using CI variables to create ACI, hosted by Azure Cloud alongside RG, VNET, VM, ACR, and ACI.

Architecture Diagram

{ "headers": [ "Component", "Action", "Outputs" ], "rows": [ [ "Developer", "Commits code", "Triggers CI/CD Pipeline" ], [ "CI/CD Pipeline", "Builds Docker image & pushes", "Image to ACR" ], [ "Terraform", "Deploys with CI variables", "ACI created" ], [ "Azure Cloud", "Hosts infrastructure", "RG, VNET, VM, ACR, ACI" ] ] }

Source: Developer → CI/CD Pipeline → Terraform → Azure Cloud (RG, VNET, VM, ACR, ACI)

The timeline depicts a CI/CD process flow: a developer commits code, triggering CI to build and push a Docker image to Azure Container Registry (ACR). Terraform then provisions an Azure Container Instance (ACI) with the image, where the application deploys and runs.

Process Flow

1: Developer Commits Code Developer pushes code changes to the version control repository. 2: CI Builds Docker Image CI pipeline automatically builds Docker image from committed code. 3: Image Pushed to ACR Built Docker image is securely pushed to Azure Container Registry. 4: Terraform Creates ACI Terraform run provisions Azure Container Instance with new image. 5: Application Runs in ACI Application deploys and starts running in the ACI environment.

The "Key Benefits" slide features a grid of five advantages: separation of concerns for better maintainability, controlled environment setups for consistency, faster CI/CD deployments, reduced misconfiguration risks, and easy rollback with scaling. These highlights emphasize reliable, efficient infrastructure and application management.

Key Benefits

{ "features": [ { "icon": "🧩", "heading": "Separation of Concerns", "description": "Isolates infrastructure from application deployments for better maintainability." }, { "icon": "🔒", "heading": "Controlled Environment Setup", "description": "Pre-configured infra ensures consistent and reliable environments every time." }, { "icon": "🚀", "heading": "Faster Deployments", "description": "CI/CD automates app rollouts, speeding up delivery significantly." }, { "icon": "🛡️", "heading": "Reduced Misconfiguration Risk", "description": "Standardized setups minimize errors and deployment failures." }, { "icon": "🔄", "heading": "Easy Rollback & Scaling", "description": "Quick recovery from issues and effortless resource scaling." } ] }

This conclusion slide summarizes the key approach as a one-time infrastructure setup paired with CI-driven app deployment. It recommends adopting deferred infrastructure creation using CI-controlled variables.

Summary

One-time infra setup + CI-driven app deployment.

Adopt Deferred Infrastructure Creation with CI-Controlled Variables.