6 Commits

Author SHA1 Message Date
9d32790c99 Move terraform-state to b2
The terraform-state can be stored in backblaze b2 with some
configurations. This changes does exactly this. Note, that this requires
the special env-variables `AWS_SECRET_ACCESS_KEY` and
`AWS_ACCESS_KEY_ID` which are normally part of the AWS-setup. To be able
to use AWS and this setup in parallel I use dotenv to maintain the
variables in the special file `.envrc`.

Reference: https://andrzejgor.ski/posts/backblaze_b2_tf_state
Reference: https://www.reddit.com/r/selfhosted/comments/1iv1qir
Reference: https://direnv.net/
2025-11-28 00:28:25 +01:00
fef383fed4 Move setup of foundational service from k8s to k3s
It simply doesn't make sense to split the installation of the
kubernetes-cluster from the provisioning of foundational services.
Therefore I drop the idea to organise these services in another
terraform-setup and instead ensure their presence with ansible, as it's
already responsible for setting up the cluster and keep it up-to.date.
2025-11-28 00:23:36 +01:00
dfcdc9797a Setup k3s with the help of ansible after the infra-provisioning
This change is huge! It allows me to manage the k3s installation on the
hetzner-cloud I setup via terraform.
2025-09-15 04:20:22 +02:00
1eb2ce341a Define a basic but working complete k3s-kubernetes setup 2025-03-10 01:44:56 +01:00
d005643bb1 Add directory for modules and move dns into it 2025-03-05 00:08:51 +01:00
3a09b0f44e Define all my DNS-records in the hetzner-cloud 2025-01-12 15:15:10 +01:00