The main purpose of this repository is to create Azure resources needed to deploy a FastAPI service to Azure Kubernetes service. The code for the FastAPI service can be found here ¹, the repository also contains Azure Pipelines to pull and push a docker image to the Azure Container Registry, and re-use use this image to deploy to the Kubernetes cluster.

The main resources created via this Terraform are:

• Azure Active Directory Applications (App registration and Enterprise application)
• Azure Kubernetes Service
• Azure Container Registry
• Azure DevOps service connections

1. Developer makes changes to the source code then pushes changes.
2. Azure pipeline triggered by new commit and starts a build on either Microsoft hosted agent or self-managed build agents.
3. Azure build agent starts and runs unit tests within the repository.
4. Azure pipeline creates a docker image, tags and pushed to an Azure container registry.
5. Azure pipeline pulls the recently pushed image and deploys to Azure Kubernetes Cluster.
6. Application is accessible from public URLs.

• terraform
• terragrunt
• pre-commit
• terraform-docs this is required for terraform_docs hooks

1. Have a Azure Portal account.
2. You will need to create a Service Principal with a Client Secret follow instructions.

1. Navigate to the environment you would like to deploy,
2. Plan your changes with terragrunt plan to see what changes will be made,
3. If you're happy with the changes terragrunt apply.

A majority of the resources created will have either be 'Standard' or 'Premium' tier. Please be mindful of the cost for each tier, Infracost has been used to help indicate how much it will cost to have all these resources created and running for a month.

 Name                                                                     Monthly Qty  Unit                  Monthly Cost

module.kubernetes_cluster.azurerm_kubernetes_cluster.cluster
├─ Uptime SLA                                                                    730  hours                       $73.00
├─ default_node_pool
│  ├─ Instance usage (Linux, pay as you go, Standard_D2_v2)                    1,460  hours                      $198.56
│  └─ os_disk
│     └─ Storage (S10, LRS)                                                        2  months                      $11.78
└─ Load Balancer
    └─ Data processed                                                Monthly cost depends on usage: $0.005 per GB

module.python_fastapi_registry.azurerm_container_registry.registry
├─ Geo replication (1 location)                                                   30  days                        $50.00
├─ Registry usage (Premium)                                                       30  days                        $50.00
├─ Storage (over 500GB)                                             Monthly cost depends on usage: $0.10 per GB
└─ Build vCPU                                                       Monthly cost depends on usage: $0.0001 per seconds

OVERALL TOTAL                                                                                                    $383.33
──────────────────────────────────
13 cloud resources were detected:
∙ 2 were estimated, all of which include usage-based costs, see https://infracost.io/usage-file
∙ 10 were free:
  ∙ 7 x azurerm_role_assignment
  ∙ 1 x azurerm_container_registry_scope_map
  ∙ 1 x azurerm_container_registry_token
  ∙ 1 x azurerm_resource_group
  ∙ 1 is not supported yet, see https://infracost.io/requested-resources:
  ∙ 1 x azurerm_container_registry_token_password

Git hook scripts are very helpful for identifying simple issues before pushing any changes. Hooks will run on every commit automatically pointing out issues in the code e.g. trailing whitespace.

To help with the maintenance of these hooks, pre-commit is used, along with pre-commit-hooks.

Please follow these instructions to install pre-commit locally and ensure that you have run pre-commit install to install the hooks for this project.

Additionally, once installed, the hooks can be updated to the latest available version with pre-commit autoupdate.

Code formatting and documentation for variables and outputs is generated using pre-commit-terraform hooks that in turn uses terraform-docs that will insert/update documentation. The following markers have been added to the README.md:

<!-- {BEGINNING|END} OF PRE-COMMIT-TERRAFORM DOCS HOOK --->