typhoon/bare-metal/fedora-atomic/kubernetes
Dalton Hubble 567e18f015 Fix conflict between Calico and NetworkManager
* 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
2018-04-25 21:45:58 -07:00
..
cloudinit Fix conflict between Calico and NetworkManager 2018-04-25 21:45:58 -07:00
kickstart Fix ostree repo to be called fedora-atomic on bare-metal 2018-04-21 18:46:56 -07:00
bootkube.tf Update Calico from v3.0.4 to v3.1.1 for Atomic 2018-04-21 18:46:56 -07:00
groups.tf Add bare-metal Fedora Atomic module 2018-04-21 18:46:56 -07:00
LICENSE Add bare-metal Fedora Atomic module 2018-04-21 18:46:56 -07:00
outputs.tf Add bare-metal Fedora Atomic module 2018-04-21 18:46:56 -07:00
profiles.tf Add atomic_assets_endpoint var for fedora-atomic bare-metal 2018-04-21 18:46:56 -07:00
README.md Update Fedora Atomic modules to Kubernetes v1.10.1 2018-04-21 18:46:56 -07:00
require.tf Add bare-metal Fedora Atomic module 2018-04-21 18:46:56 -07:00
ssh.tf Use bootkube system container on fedora-atomic 2018-04-21 18:46:56 -07:00
variables.tf Add atomic_assets_endpoint var for fedora-atomic bare-metal 2018-04-21 18:46:56 -07:00

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

Docs

Please see the official docs and the bare-metal tutorial.