{"push_id":2141423061,"size":1,"distinct_size":1,"ref":"refs/heads/external","head":"8a6a07f0b696b6cabcb8f6cadebf00c45c2544ca","before":"bbdb8274f4823d9b618756329008a567230a0e96","commits":[{"sha":"8a6a07f0b696b6cabcb8f6cadebf00c45c2544ca","author":{"name":"Walter Fender","email":"997f9439ab2ea0de14b116589035f56ff888aa9e@google.com"},"message":"Seperate loop and plugin control\n\nSeperate loop and plugin control in the kube-controller-manager.\nAdding an \"--external-plugin\" flag to specify a plugin to load when\ncloud-provider is set to \"external\". Flag has no effect currently\nwhen the cloud-provider is not set to external. The expectation is\nthat the cloud provider and external plugin flags would go away once\nall cloud providers are on stage 2 cloud-controller-manager solutions.\n\nManaging the control loops more directly based on start up flags.\nAddressing issue brought up by @wlan0\n\nSwitched to using the main node controller in CCM.\nChanges to enable full NodeController to start in CCM.\nFix related tests.\nUnifying some common code between KCM and CCM.\nFix related tests and comments.\nFolded in feedback from @jhorwit2 and @wlan0","distinct":true,"url":"https://api.github.com/repos/cheftako/kubernetes/commits/8a6a07f0b696b6cabcb8f6cadebf00c45c2544ca"}]}
{"actor":{"display_login":"cheftako"}}