khuedoan-homelab/external
Khue Doan dc7d1256a0 build: set kubeconfig from global Makefile
Separate build steps in Tekton can use service account instead of config file
2022-05-14 20:06:57 +07:00
..
modules/cloudflare chore(deps): update all non-major dependencies helm releases 2022-03-23 15:07:13 +00:00
.gitignore fix(external): fix wrong provider name for B2 2021-12-09 01:23:04 +07:00
main.tf refactor(external)!: use separate modules for each provider 2022-03-14 23:21:28 +07:00
Makefile build: set kubeconfig from global Makefile 2022-05-14 20:06:57 +07:00
namespaces.yml feat(external): inject Backblaze secrets to k8up namespace 2021-12-25 20:18:45 +07:00
README.md refactor(external): remove Backblaze B2 2022-03-14 23:07:59 +07:00
terraform.tfvars.j2 refactor(external): remove Backblaze B2 2022-03-14 23:07:59 +07:00
tfvars.yml refactor(external): remove Backblaze B2 2022-03-14 23:07:59 +07:00
variables.tf refactor(external): remove Backblaze B2 2022-03-14 23:07:59 +07:00
versions.tf chore(deps): update all non-major dependencies helm releases 2022-03-23 15:07:13 +00:00

External resources

WIP documents

These resources are optional, the homelab still works without them but will lack some features like trusted certificates and offsite backup

Although I try to keep the amount of external resources to the minimum, there's still need for a few of them. Below is a list of external resources and why we need them (also see some alternatives below).

  • Terraform Cloud:
    • Workspace to store the state for external resources
  • Cloudflare:
    • DNS
    • DNS-01 challenge for Let's Encrypt
    • Tunnel to public services to the internet without port-forwarding
  • AWS:
    • S3 Glacier for offsite backup

This layer will:

  • Create external resources
  • Add external secrets to namespaces

Prerequisites

Create Terraform workspace

Terraform is stateful, which means it needs somewhere to store it's state. The Terraform Cloud is one option for a state backend with a generous free tier perfect for a homelab.

  1. Sign up for a Terraform Cloud
  2. Create a workspace named homelab-external, this is the workspace where your homelab state will be stored.
  3. Change the "Execution Mode" from "Remote" to "Local". This will ensure your local machine, which can access your lab, is the one executing the terraform plan rather than the cloud runners.

If you decide to use a different terraform backend, you'll need to edit the external/versions.tf file as required.

Create Cloudflare API token

https://dash.cloudflare.com/profile/api-tokens

Terraform API token summary:

This API token will affect the below accounts and zones, along with their respective permissions

└── Khue Doan - Argo Tunnel:Edit, Account Settings:Read
    └── khuedoan.com - Zone:Read, DNS:Edit

Client IP Address Filtering

└── Is in - 117.xxx.xxx.xxx, 2402:xxx:xxx:xxx:xxx:xxx:xxx:xxx

Create AWS API key

TODO

Deploy

Apply Terraform (you will be prompted to login to Terraform Cloud and enter API keys from the previous steps):

make

Alternatives

  • Terraform Cloud: any other Terraform backends
  • Cloudflare Tunnel: you can build a small VPS in the cloud and route traffic via it using Wireguard and HAProxy.
  • S3 Glacier: any S3 compatible object storage, such as Backblaze B2, Minio...