be29f52039
* Add an `enable_aggregation` variable to enable the kube-apiserver aggregation layer for adding extension apiservers to clusters * Aggregation is **disabled** by default. Typhoon recommends you not enable aggregation. Consider whether less invasive ways to achieve your goals are possible and whether those goals are well-founded * Enabling aggregation and extension apiservers increases the attack surface of a cluster and makes extensions a part of the control plane. Admins must scrutinize and trust any extension apiserver used. * Passing a v1.14 CNCF conformance test requires aggregation be enabled. Having an option for aggregation keeps compliance, but retains the stricter security posture on default clusters |
||
|---|---|---|
| .. | ||
| cl | ||
| workers | ||
| LICENSE | ||
| README.md | ||
| bootkube.tf | ||
| controllers.tf | ||
| lb.tf | ||
| network.tf | ||
| outputs.tf | ||
| require.tf | ||
| security.tf | ||
| ssh.tf | ||
| variables.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.14.0 (upstream, via kubernetes-incubator/bootkube)
- Single or multi-master, flannel networking
- On-cluster etcd with TLS, RBAC-enabled
- Advanced features like worker pools, low-priority workers, and snippets customization
- Ready for Ingress, Prometheus, Grafana, and other optional addons
Docs
Please see the official docs and the Azure tutorial.