Building upon the findings from the DevOps Research and Assessment (DORA) program, this repo demonstrates an example approach for implementing an Infrastructure as Code strategy using Google Cloud.

This repo contains an example deployment approach using a combination of Terraform and Kubernetes Resource Model (KRM). Terraform is used to deploy the base infrastructure (GKE, Config Connector) and KRM is used to deploy applications (Kubernetes Deployments/Services) and application depedencies (Cloud Firestore).

1. A Google Cloud project with billing set up.
2. gcloud
3. kubectl
4. terraform

The Terraform in the infra directory does the following:

• Creates a 3-node zonal GKE cluster
• Configures Workload Identity
• Enables the Config Connector add-on
• Creates a service account and service account bindings for Config Connector
• Creates the required Config Connector resources, necessary to complete deployment

Change to the infra directory:

cd infra/

Update the region, zone, and deployment_name input variables in terraform.tfvars. Then, initialize the Terraform bits:

terraform init

When that's completed, you'll have the necessary providers and modules to deploy.

Now use Terraform's plan mechanism to see what changes will be made:

terraform plan -var project_id=PROJECT_ID

Assuming that all looks good, go ahead and deploy:

terraform apply -auto-approve -var project_id=PROJECT_ID

Once the deployment is complete, we need to complete the Config Connector setup process. But first, setup kubectl:

gcloud container clusters get-credentials adora-iac-cluster --zone ZONE

Now apply the remaining resources to complete the setup:

kubectl apply -f configconnector.yaml
kubectl apply -f namespace.yaml

TODO

TODO

terraform destroy