dniel/terraform repository overview

⁠Terraform

This repo contains my Terraform scripts that deployes all Kubernetes manifests to my k8s clusters. Providers used to deploy manifests to Kubernetes.

• Official Kubernetes provider for k8s resources.⁠
• Alpha Kubernetes provider for generic k8s manifests.⁠
• Auth0 provider to create clients and resource servers.⁠
• Community Helm Provider for deploying Helm charts.⁠
• Official AWS provider to handle Route53 registration of applications.⁠

⁠Kubernetes deployment

The terraform scripts does NOT contain the provisioning of Kubernetes itself. I have two clusters running, one in Amazon EKS deployed by cloudformation and one on-prem on VMWare deployed with Canonical JUJU.

⁠Init manifests

Some stuff I havent managed yet to deploy with Terraform and will ned to be deployed to Kubernetes manually with kubectl before running Terraform. The directory init contains manifests for k8s and should be deployed using kubectl create -f init/ before running terraform apply.

⁠Environments

I run several deployments at the same time, both on-prem in parallel and in Amazon EKS. Under the directory envs there is one directory for each deployment.

• cloud is deployed to Amazon.
• cloud-services is a shared services stack in the cloud.
• home is my primary deployment on-prem.
• home-services is a shared services stack at home.

To deploy an environment its meant to stand in its directory and do terraform apply Secrets are stored in encrypted files in the repo and contains a couple of variables that are needed to run the terraform scripts.

⁠Templates

Two different default templates to configure an environment with.

⁠template

Is a small and mostly empty base template. It contains common stuff like a default configuration of traefik and forwardauth and not much more.

⁠template-services

Is a more specialized template that contains some applications that are meant to be installed just once for each cluster and contains common tools like prometheus, grafana.

⁠Modules

Under modules I have put all my re-usable code, the environments should not contain much code itself but should instead use the modules to configure deploy the software.