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
..
container-linux/kubernetes	Update Calico from v3.0.4 to v3.1.1	2018-04-21 18:30:36 -07:00
fedora-atomic/kubernetes	Fix conflict between Calico and NetworkManager	2018-04-25 21:45:58 -07:00