scottk/terraform-talos
1
0
Fork 0
mirror of https://github.com/optim-enterprises-bv/terraform-talos.git synced 2025-11-01 02:38:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update doc

Browse Source
This commit is contained in:
Serge Logvinov
2022-06-11 18:38:41 +03:00
parent e3af52356f
commit b438baefa0
1 changed files with 29 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
README.md
View File

@@ -4,8 +4,32 @@ I store here the terraform code to launch Talos in the clouds.
I wouldn't use the terrafrom modules from internet. I wouldn't use the terrafrom modules from internet.
The goal is to create all cloud services from scratch. The goal is to create all cloud services from scratch.
* [GCP](gcp-zonal) - one region, many zones. Well tested with talos 0.14.0 * [Azure](azure) - many regions, many zones.
* [Hetzner](hetzner) - many regions. Well tested with talos 0.14.0 Well tested with talos 1.1.x.
* [Openstack](openstack) - many regions, many zones. Well tested with talos 1.1.x Platform addons: CCM,CSI,Autoscaler
* [Oracle](oracle) - many regions, many zones. Well tested with talos 1.0.0 * [GCP](gcp-zonal) - one region, many zones.
* [Scaleway](scaleway) - many regions. Well tested with talos 1.0.0 Well tested with talos 0.14.0.
Platform addons: CCM,CSI,Autoscaler
* [Hetzner](hetzner) - many regions.
Well tested with talos 0.14.0.
Platform addons: CCM,CSI,Autoscaler
* [Openstack](openstack) - many regions, many zones.
Well tested with talos 1.1.x.
Platform addons: CCM,CSI
* [Oracle](oracle) - many regions, many zones.
Well tested with talos 1.0.0.
* [Scaleway](scaleway) - many regions.
Well tested with talos 1.0.0.
Platform addons: CCM
## Common
* **cilium** network with vxlan tunnels.
* **ingress-nginx** (daemonsets) runs on ```web``` role nodes.
It uses ```hostNetwork``` ports 80,443 for optimizations.
It helps me to tweak the kernel on a host and apply it to ingress controller.
And I can disable conntrack too.
* **coredns-local** (daemonsets) uses dummy interface on al nodes and has ip ```169.254.2.53```
It increases the dns response (all traffic does not leave the node).
It makes sense in multi-cloud setup. Kubernets still does not have geo-based load balancer capabilities (alfa).
* **rancher.io/local-path** as default storage class.