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
d083b9d446
Make every important setting of the k8s-cluster configurable
...
This change makes all the settings configurable. The only part which
still lacks some flexibility is the location, though I really don't need
to run a k8s-cluster over multiple datacenters and regions! - At least
right now ;-)
2025-09-15 03:43:05 +02:00
998426c330
Add variable to decide wether the ssh-port of the k8s-server is exposed
2025-09-14 16:26:11 +02:00
8797fad6d7
Update costs-table of domains to read the prices easier
2025-04-23 23:17:21 +02:00
a1e9f43a31
reorganize firewall rules to make it more obvious what has changed
2025-03-15 20:49:40 +01:00
1eb2ce341a
Define a basic but working complete k3s-kubernetes setup
2025-03-10 01:44:56 +01:00
2d93766c09
Add ssh-keys to hetzner-cloud
2025-03-08 21:37:15 +01:00
f37c92c439
Reduce number of terraform-file to the "normal" set of files and simplify dns-definition
2025-03-08 21:36:43 +01:00
4b7bb428a7
Use most recent configuration of gmail-smtp
...
The configuration of MX records for gmail has changed in 2023. Although
google still maintains the old configuration the recommended approach is
the new variant, which is also more concise.
Reference: https://support.google.com/a/answer/174125?hl=en#zippy=%2Cgoogle-workspace-legacy-version-before%2Cgoogle-workspace-current-version-later
2025-03-05 00:08:51 +01:00
d005643bb1
Add directory for modules and move dns into it
2025-03-05 00:08:51 +01:00
817f75bb49
Refactor DNS-config to make it easier to maintain
2025-03-04 23:15:42 +01:00
3a09b0f44e
Define all my DNS-records in the hetzner-cloud
2025-01-12 15:15:10 +01:00
266c422c28
Initial commit
2025-01-06 00:29:54 +01:00
