567e18f015
* Observed frequent kube-scheduler and controller-manager restarts with Calico as the CNI provider. Root cause was unclear since control plane was functional and tests of pod to pod network connectivity passed * Root cause: Calico sets up cali* and tunl* network interfaces for containers on hosts. NetworkManager tries to manage these interfaces. It periodically disconnected veth pairs. Logs did not surface this issue since its not an error per-se, just Calico and NetworkManager dueling for control. Kubernetes correctly restarted pods failing health checks and ensured 2 replicas were running so the control plane functioned mostly normally. Pod to pod connecitivity was only affected occassionally. Pain to debug. * Solution: Configure NetworkManager to ignore the Calico ifaces per Calico's recommendation. Cloud-init writes files after NetworkManager starts, so a restart is required on first boot. On subsequent boots, the file is present so no restart is needed |
||
|---|---|---|
| .. | ||
| cloudinit | ||
| workers | ||
| LICENSE | ||
| README.md | ||
| apiserver.tf | ||
| bootkube.tf | ||
| controllers.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.10.0 (upstream, via kubernetes-incubator/bootkube)
- Single or multi-master, workloads isolated on workers, Calico or flannel networking
- On-cluster etcd with TLS, RBAC-enabled, network policy
- Ready for Ingress, Prometheus, Grafana, and other optional addons
Docs
Please see the official docs and the Google Cloud tutorial.