291107e4c9
* With Cilium v1.14, Cilium's kube-proxy partial mode changed to either be enabled or disabled (not partial). This somtimes leaves Cilium (and the host) unable to reach the kube-apiserver via the in-cluster Kubernetes Service IP, until the host is rebooted * As a workaround, configure Cilium to rely on external DNS resolvers to find the IP address of the apiserver. This is less portable and less "clean" than using in-cluster discovery, but also what Cilium wants users to do. Revert this when the upstream issue https://github.com/cilium/cilium/issues/27982 is resolved |
||
---|---|---|
.. | ||
butane | ||
workers | ||
LICENSE | ||
README.md | ||
ami.tf | ||
bootstrap.tf | ||
controllers.tf | ||
network.tf | ||
nlb.tf | ||
outputs.tf | ||
security.tf | ||
ssh.tf | ||
variables.tf | ||
versions.tf | ||
workers.tf |
README.md
Typhoon
Typhoon is a minimal and free Kubernetes distribution.
- Minimal, stable base Kubernetes distribution
- Declarative infrastructure and configuration
- Free (freedom and cost) and privacy-respecting
- Practical for labs, datacenters, and clouds
Typhoon distributes upstream Kubernetes, architectural conventions, and cluster addons, much like a GNU/Linux distribution provides the Linux kernel and userspace components.
Features
- Kubernetes v1.28.3 (upstream)
- Single or multi-master, Calico or Cilium or flannel networking
- On-cluster etcd with TLS, RBAC-enabled, network policy
- Advanced features like worker pools, spot workers, and snippets customization
- Ready for Ingress, Prometheus, Grafana, CSI, and other optional addons
Docs
Please see the official docs and the AWS tutorial.