60c70797ec
* Use a single admin kubeconfig for initial bootkube bootstrap and for use by a human admin. Previously, an admin kubeconfig without a named context was used for bootstrap and direct usage with KUBECONFIG=path, while one with a named context was used for `kubectl config use-context` style usage. Confusing. * Provide the admin kubeconfig via `assets/auth/kubeconfig`, `assets/auth/CLUSTER-config`, or output `kubeconfig-admin` |
||
|---|---|---|
| .. | ||
| cloudinit | ||
| workers | ||
| LICENSE | ||
| README.md | ||
| apiserver.tf | ||
| bootkube.tf | ||
| controllers.tf | ||
| ingress.tf | ||
| network.tf | ||
| outputs.tf | ||
| require.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.13.1 (upstream, via kubernetes-incubator/bootkube)
- Single or multi-master, Calico or flannel networking
- On-cluster etcd with TLS, RBAC-enabled, network policy
- Advanced features like worker pools and preemptible workers
- Ready for Ingress, Prometheus, Grafana, and other optional addons
Docs
Please see the official docs and the Google Cloud tutorial.