Skip to content

Latest commit

 

History

History
60 lines (37 loc) · 3.6 KB

README.md

File metadata and controls

60 lines (37 loc) · 3.6 KB
Raw

Infrastructure

This directory houses the code that transforms raw bare-metal machines into functional Kubernetes clusters. The code in this directory depends on a LAN-accessible Proxmox VE installation (or multiple!) to create a bare-bones Kubernetes cluster using Talos.

Prerequisites

  1. Terraform installed (check the providers file for the specific version requirements)

  2. Install Proxmox VE v8.0+ on a bare-metal machine (or more than one).

  3. Ensure you have a file named aws-credentials in the talos directory in the format:

    [default]
aws_access_key_id = <redacted>
aws_secret_access_key = <redacted>

    This provides authentication to the AWS S3 bucket backend that stores the TF state AND the KMS secret to decrypt the sops file.

How To Use

  1. Populate main.tf as desired.

  2. Run the desired Terraform commands (i.e. terraform plan, terraform apply).

  3. Once the Kubernetes cluster is successfully applied, run this command to get the necessary configs loaded into your shell:

    ./get_configs

  4. Once the cluster is up and running, make sure to create the necessary Flux secret so that Flux can access the Git repository. Docs here.

Operations

To add new nodes with new disks

  1. Navigate to relevant node in Proxmox GUI -> Disks -> LVM-Thin -> Create: Thinpool
  2. Select new disk by block device name (lsblk might help show available nodes on the node). Example names: /dev/sda, /dev/sdb, /dev/sdc.
  3. Give the disk a name. I've chosen to increment the disks by the bay #. Example: Bay #3 -> disk3
  4. Hit "Create".

Upgrading Kubernetes

Can perform a rolling upgrade with the TF provider and a standard TF workflow (or talosctl also works per the docs).

Upgrade Talos

The Talos TF provider is relatively under-featured for upgrades (Example of lack of features here). So it's best to use talosctl and follow the more production-ready upgrade path here.

Upgrading Talos-Controlled, Kubernetes-State-Managed Resources

There are some Kubernetes configurations, such as the kube-proxy configuration, which talosctl manages but only touches during Kubernetes bootstraps/upgrades. Here is a good example. To update a resource whose state is entirely within Kubernetes, but the config is managed via Talos, refer to the upgrading Kubernetes section above

TODOs

  1. Enable Talos logs to be sent to a logging endpoint, similar to this example.

Notes

IP Declaration

I attempted for quite a while to avoid tedious manual declarations of IP addresses for each Kubernetes node. I found some level of success assigning MAC addresses to the VMs, reading the DHCP-assigned IPv4 addresses from the Unifi Router, then using that in the rest of the progress. But ultimately it was unsuccessful. The Unifi Router would begin to get confused with the introduction of virtual IPs, such as the Talos Virtual IP, and begin to return the Virtual IP when I needed the direct node IP. I had to scrap this idea unfortunately. Now we must assign each node an IP address and MAC address in main.tf manually.