{"push_id":1904866174,"size":4,"distinct_size":4,"ref":"refs/heads/master","head":"9f079975be1d0eb88e1ea33681e90d12078ffaab","before":"0942ae378360dbed658ab98d01edfe2dde492f28","commits":[{"sha":"32502ad54f477cd75f4fc4d21e686190842a077c","author":{"name":"Prachetas Prabhu","email":"b78e5c4a23bfbb22a3e1999e3b3e711d923714b1@gmail.com"},"message":"Adds wider tolerations to Canal Daemonset to allow scheduling on nodes with strict taints","distinct":true,"url":"https://api.github.com/repos/kubernetes/kops/commits/32502ad54f477cd75f4fc4d21e686190842a077c"},{"sha":"8f13944ac3b371645ef8309d0eacdcbe2a98a132","author":{"name":"Prachetas Prabhu","email":"b78e5c4a23bfbb22a3e1999e3b3e711d923714b1@gmail.com"},"message":"Bumps calico versions to mitigate taint stripping issue","distinct":true,"url":"https://api.github.com/repos/kubernetes/kops/commits/8f13944ac3b371645ef8309d0eacdcbe2a98a132"},{"sha":"76378da0d0bae1cd792fea5edbf72f8767e7c75d","author":{"name":"Prachetas Prabhu","email":"b78e5c4a23bfbb22a3e1999e3b3e711d923714b1@gmail.com"},"message":"Bumps version of Canal manifest addon to upgrade Canal on existing clusters","distinct":true,"url":"https://api.github.com/repos/kubernetes/kops/commits/76378da0d0bae1cd792fea5edbf72f8767e7c75d"},{"sha":"9f079975be1d0eb88e1ea33681e90d12078ffaab","author":{"name":"Kubernetes Submit Queue","email":"260061d766fe633e5411cb223defd984f1ece7b6@users.noreply.github.com"},"message":"Merge pull request #3142 from prachetasp/psp/canal-tolerations\n\nAutomatic merge from submit-queue\n\nFix for Canal Taints and Tolerations\n\nThis PR fixes issues with taints and tolerations for the Canal network type.\r\n\r\nThere are 2 problems:\r\n\r\n1. Canal pods will not schedule onto dedicated instancegroups due to their too-strict tolerations. A similar fix for calico was merged recently #3097 - this is the same fix for Canal instead.\r\n2. When booting a cluster with 1.7.0 we ran into the same issue mentioned in projectcalico/canal#77 and likely experienced in #2856. Specifically one of our dedicated instancegroups and the master nodes had no Taints attached. To mitigate we simply bump the versions of calico/node and calico/cni to match the versions that resolved projectcalico/canal#77.\r\n\r\nWhen using these fixes to boot our k8s 1.7.3 cluster with this branch the Taints showed up and Calico scheduled on our masters and our dedicated IG.\r\n\r\nI am not sure if there are associated tests that need to be updated here - still not familiar enough with the kops repo to tell.","distinct":true,"url":"https://api.github.com/repos/kubernetes/kops/commits/9f079975be1d0eb88e1ea33681e90d12078ffaab"}]}
{"actor":{"display_login":"k8s-merge-robot"}}