.github | ||
bare-metal/container-linux | ||
digital-ocean/container-linux/kubernetes | ||
google-cloud/container-linux | ||
CONTRIBUTING.md | ||
DCO | ||
LICENSE | ||
README.md |
Typhoon
- Minimal, stable base Kubernetes distribution
- Declarative infrastructure and configuration
- Practical for small labs to medium clusters
- 100% free components (both freedom and zero cost)
- Respect for privacy by requiring analytics be opt-in
Status
Typhoon is dghubble's personal Kubernetes distribution. It powers his cloud and colocation clusters. While functional, it is not yet suited for the public.
Features
- Kubernetes v1.7.3 with self-hosted control plane via kubernetes-incubator/bootkube
- Secure etcd with generated TLS certs, RBAC-enabled, generated admin kubeconfig
- Multi-master, workload isolation
- Ingress-ready (perhaps include by default)
- Works with your existing Terraform infrastructure and secret management
Modules
Typhoon provides a Terraform Module for each supported operating system and platform.
Platform | Operating System | Terraform Module |
---|---|---|
Bare-Metal | Container Linux | bare-metal/container-linux/kubernetes |
Google Cloud | Container Linux | google-cloud/container-linux/kubernetes |
Digital Ocean | Container Linux | digital-ocean/container-linux/kubernetes |
Customization
To customize clusters in ways that aren't supported by input variables, fork the repo and make changes to the Terraform module. Stay tuned for improvements to this strategy since its beneficial to stay close to this upstream.
To customize lower-level Kubernetes control plane bootstrapping, see the poseidon/bootkube-terraform Terraform module.
Social Contract
A formal social contract is being drafted, inspired by the Debian Social Contract.
For now, know that typhoon
is not a product, trial, or free-tier. It is not run by a company, it does not offer support or services, and it does not accept or make any money. It is not associated with any operating system or cloud platform vendors.
Disclosure: The author works for CoreOS, but that work is kept as separate as possible. Support for Fedora is planned to ensure no one distro is favored and because the author wants it.
Non-Goals
- In-place Kubernetes upgrades (instead, deploy blue/green clusters and failover)