{"push_id":1347461408,"size":49,"distinct_size":2,"ref":"refs/heads/co2","head":"51e1e3e63c1161205e672512073ffdcb21a30841","before":"cfea5b2bda4d277b7bfa246f6ed91bf1030db572","commits":[{"sha":"b118db0a172f213d02e4b19f6dbf289e558e8158","author":{"name":"lojies","email":"ce192c1ad96982734e98554810974a17827ec02e@zte.com.cn"},"message":"Use dedent for completion.go","distinct":false,"url":"https://api.github.com/repos/mbohlool/kubernetes/commits/b118db0a172f213d02e4b19f6dbf289e558e8158"},{"sha":"b629ab87141745df18854014f8e89bd6f01f5a25","author":{"name":"Alan Grosskurth","email":"f4f6f056d216de93bb2209751a0d70829f609a92@google.com"},"message":"kube-dns: Add --dns-bind-address flag\n\nCurrently, kube-dns always binds to 0.0.0.0 when starting the SkyDNS\nserver. Sometimes its useful to have it bind to a different address for\ntesting. So add a new --dns-bind-address flag that can be used to\nconfigure this (default is 0.0.0.0).","distinct":false,"url":"https://api.github.com/repos/mbohlool/kubernetes/commits/b629ab87141745df18854014f8e89bd6f01f5a25"},{"sha":"112a3f3fafe43b5936551f503b49422835c03f23","author":{"name":"Alan Grosskurth","email":"f4f6f056d216de93bb2209751a0d70829f609a92@google.com"},"message":"known-flags.txt: Add --dns-bind-address\n\nThis is a newly-added kube-dns flag.","distinct":false,"url":"https://api.github.com/repos/mbohlool/kubernetes/commits/112a3f3fafe43b5936551f503b49422835c03f23"},{"sha":"f2ae2cad0bf6923c966eeacd1e5159657d42427e","author":{"name":"Robin Gloster","email":"a209d095be814acc14c37095d428b66d088728c1@mayflower.de"},"message":"kubeadm: fix typo","distinct":false,"url":"https://api.github.com/repos/mbohlool/kubernetes/commits/f2ae2cad0bf6923c966eeacd1e5159657d42427e"},{"sha":"d5e0b1cf848f0a1e9f70dbba8960c26fdb53b0bc","author":{"name":"Joe Finney","email":"bc06a6b42126300a104d627471fbb1ab91d1daa2@google.com"},"message":"Dump node info after cluster up.","distinct":false,"url":"https://api.github.com/repos/mbohlool/kubernetes/commits/d5e0b1cf848f0a1e9f70dbba8960c26fdb53b0bc"},{"sha":"e23a27f8d3f119cc7e668460088d7997ea521bb3","author":{"name":"Klaus Ma","email":"af4d9cae5513a6bac3198db542383c0266299053@gmail.com"},"message":"Added DEFAULT_NETWORK_IF_NAME when starting nodes.","distinct":false,"url":"https://api.github.com/repos/mbohlool/kubernetes/commits/e23a27f8d3f119cc7e668460088d7997ea521bb3"},{"sha":"2c797a80af26ce7f0880a6126deae877c8278b6e","author":{"name":"Michail Kargakis","email":"507be340a25d4f31d599588ff525ee75ea514bb9@redhat.com"},"message":"Revert \"Error out when any RS has more available pods then its spec replicas\"\n\nThis reverts commit 32ababbe1b0bf9ee6786aa555cc3cd7f54f2014a.","distinct":false,"url":"https://api.github.com/repos/mbohlool/kubernetes/commits/2c797a80af26ce7f0880a6126deae877c8278b6e"},{"sha":"94014159914845135a6bf507bddfa220156b9324","author":{"name":"Elson Rodriguez","email":"f44125ab2b23a26257648ca1e19dadde7a47bdfd@gmail.com"},"message":"Updating Spark Example.\n\nFew usability improvements:\n\n- Added a proxy to enable viewing worker logs\n- Removed seperate webui service\n- Modified Zeppelin and spark-ui services to be Loadbalancers\n- Changed pyspark example to be platform agnostic\n- Improved kubectl context setup\n- Minor grammar/flow fixes","distinct":false,"url":"https://api.github.com/repos/mbohlool/kubernetes/commits/94014159914845135a6bf507bddfa220156b9324"},{"sha":"cde5559d0951a2e78d24ef1055adfa432de80b3a","author":{"name":"Jess Frazelle","email":"fa4bef09f4df487cf2d3f52ab73533c8b26212dc@google.com"},"message":"Update `gcloud docker` commands to use `gcloud docker -- ARGS`\n\nWe can then avoid the following warning:\n```\nWARNING: The '--' argument must be specified between gcloud specific args on the left and DOCKER_ARGS on the right. IMPORTANT: previously, commands allowed the omission of the --, and unparsed arguments were treated as implementation args. This usage is being deprecated and will be removed in March 2017.\nThis will be strictly enforced in March 2017. Use 'gcloud beta docker' to see new behavior.\n```\n\nSigned-off-by: Jess Frazelle <acidburn@google.com>","distinct":false,"url":"https://api.github.com/repos/mbohlool/kubernetes/commits/cde5559d0951a2e78d24ef1055adfa432de80b3a"},{"sha":"58d25e378c4f76c087b10fe624f6fa64879292ad","author":{"name":"Mike Danese","email":"bc4bc6c0830ac6a1b78106039db8e71a24949f13@google.com"},"message":"kubeadm: allow kubeadm init to read config from file","distinct":false,"url":"https://api.github.com/repos/mbohlool/kubernetes/commits/58d25e378c4f76c087b10fe624f6fa64879292ad"},{"sha":"53e393ad421394ad664da09bbab86bf6f1d458e1","author":{"name":"Ilya Dmitrichenko","email":"e95508e55b7ca46cd4b27799f75e0dd544b3e563@gmail.com"},"message":"Test API more extensivelly before declaring readiness (close #34411)","distinct":false,"url":"https://api.github.com/repos/mbohlool/kubernetes/commits/53e393ad421394ad664da09bbab86bf6f1d458e1"},{"sha":"5c66dcb52618e6c17f0a3068dc7c1be551777ade","author":{"name":"pweil-","email":"d0a9729d726e155b7272cd1f26229e0f1df76fce@redhat.com"},"message":"inject authorizer when admission controller requests it","distinct":false,"url":"https://api.github.com/repos/mbohlool/kubernetes/commits/5c66dcb52618e6c17f0a3068dc7c1be551777ade"},{"sha":"6406aacb598a6e94118c944dedf5132320632fa8","author":{"name":"deads2k","email":"9eea6a26ae0243814229a46d171002f67ac6168a@redhat.com"},"message":"remove legacy API prefix from generic","distinct":false,"url":"https://api.github.com/repos/mbohlool/kubernetes/commits/6406aacb598a6e94118c944dedf5132320632fa8"},{"sha":"113c5e34751bf394eb5a2b8fb398cec851f4daa1","author":{"name":"Cole Mickens","email":"62cd730ab4caf717f21adea75e83dade15a81fc2@gmail.com"},"message":"azure: filter load balancer backend nodes to PrimaryAvailabilitySet if set","distinct":false,"url":"https://api.github.com/repos/mbohlool/kubernetes/commits/113c5e34751bf394eb5a2b8fb398cec851f4daa1"},{"sha":"661d6bde6fb2c59393d4742d23c71c67f3b5b5fc","author":{"name":"Jeff Grafton","email":"37780e769b84e50aeec1ef2668f6dba1732f01bc@google.com"},"message":"Delete all firewall rules and network on GCE/GKE test cluster teardown","distinct":false,"url":"https://api.github.com/repos/mbohlool/kubernetes/commits/661d6bde6fb2c59393d4742d23c71c67f3b5b5fc"},{"sha":"ee6e92473d24c30417f49ca261fa7c436551fc48","author":{"name":"Jeff Grafton","email":"37780e769b84e50aeec1ef2668f6dba1732f01bc@google.com"},"message":"gcloud compute instances list --zone -> --zones","distinct":false,"url":"https://api.github.com/repos/mbohlool/kubernetes/commits/ee6e92473d24c30417f49ca261fa7c436551fc48"},{"sha":"2202688eefed1547c3591574b6f043d1b377922f","author":{"name":"Yu-Ju Hong","email":"bad283af5617eff6e3a0e5eaae12ca0d9ff08551@google.com"},"message":"Add more log messages for sandbox restarts","distinct":false,"url":"https://api.github.com/repos/mbohlool/kubernetes/commits/2202688eefed1547c3591574b6f043d1b377922f"},{"sha":"fd5cfb37f37da855be2157a9fe08229ea87202a3","author":{"name":"Kubernetes Submit Queue","email":"260061d766fe633e5411cb223defd984f1ece7b6@users.noreply.github.com"},"message":"Merge pull request #33604 from elsonrodriguez/spark-update\n\nAutomatic merge from submit-queue\n\nUpdating Spark Example.\n\nFew usability improvements:\r\n\r\n- Added a proxy to enable viewing worker logs\r\n- Removed seperate webui service\r\n- Modified Zeppelin and spark-ui services to be Loadbalancers\r\n- Changed pyspark example to be platform agnostic\r\n- Minor grammar/flow fixes","distinct":false,"url":"https://api.github.com/repos/mbohlool/kubernetes/commits/fd5cfb37f37da855be2157a9fe08229ea87202a3"},{"sha":"4a223efd2706b3ef437afdef28d4e650d5e36d66","author":{"name":"Kubernetes Submit Queue","email":"260061d766fe633e5411cb223defd984f1ece7b6@users.noreply.github.com"},"message":"Merge pull request #34573 from errordeveloper/fix-early-deployment-issue\n\nAutomatic merge from submit-queue\n\nTest API more extensivelly before declaring readiness \n\n**What this PR does / why we need it**:\r\n\r\nIt's possible that first deployment kubeadm creates will hit `deployments.extensions \"kube-discovery\" is forbidden: not yet ready to handle request`, which comes from NamespaceLifecycle admission controller and has something to do with cache. According to @derekwaynecarr, we need to create a namespace-scoped resource to really check for this. I didn't want to make a check with deployment of whatever comes first right now, and decided to have explicit step for this in `apiclient.go`.\r\n\r\n**Which issue this PR fixes**: fixes #34411\r\n\r\n**Special notes for your reviewer**: @kubernetes/sig-cluster-lifecycle \r\n\r\n**Release note**:\r\n```release-note\r\nNONE\r\n```","distinct":false,"url":"https://api.github.com/repos/mbohlool/kubernetes/commits/4a223efd2706b3ef437afdef28d4e650d5e36d66"},{"sha":"3b787c9b3d12d2cae3db99939f7f5b755c59103c","author":{"name":"Kubernetes Submit Queue","email":"260061d766fe633e5411cb223defd984f1ece7b6@users.noreply.github.com"},"message":"Merge pull request #34526 from colemickens/colemickens-azure-specify-availabilityset\n\nAutomatic merge from submit-queue\n\nazure: filter load balancer backend nodes to PrimaryAvailabilitySet (if set)\n\n<!--  Thanks for sending a pull request!  Here are some tips for you:\r\n1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md\r\n2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md\r\n3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes\r\n-->\r\n\r\n**What this PR does / why we need it**:\r\n- Adds a new field (`PrimaryAvailabilitySetName`) to the Azure CloudProvider config struct\r\n- If the field is set, only machines who are in that availabilitySet are added to the load balancer backend pool.\r\n\r\nThis is required to:\r\n- Support more than 100 nodes in Azure (only can have 100 nodes per availability set)\r\n- Support multiple availability sets per cluster (An Azure L4 LoadBalancer can only be pointed at nodes in a single availability set)\r\n\r\nWithout this PR, or if the field is **not** set in a cluster that contains two availabilitysets, then the following is observed:\r\n- Azure resources are created (LB, LB rules, NSG rules, public IP)\r\n- Azure throws errors when trying to add nodes from the \"other\" availability set\r\n- The service winds up exposed to the outside world (if you manually retrieve the public ip from Azure API)\r\n- Kubernetes controller-manager's service loop keeps retrying forever because it never finishes fully successfully\r\n- The \"external ip\" property field is never updated.\r\n\r\n**Which issue this PR fixes**: Fixes #34293\r\n\r\n**Unknowns**:\r\n- Naming convention: `LoadBalancedAvailabilitySet` might be more descriptive than `PrimaryAvailabilitySet`, but is also a misnomer since `kube-proxy` will still end up routing requests to all relevant nodes.\r\n- Is it worth trying to be \"smart\" about it in the case the user hasn't set this field in the config? Save the first availability set name and try not to add any nodes that aren't also in that one? It may simply be better to just let this fail so the user has to choose the right setting for their use-case.\r\n\r\n**Release note**:\r\n<!--  Steps to write your release note:\r\n1. Use the release-note-* labels to set the release note state (if you have access) \r\n2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. \r\n-->\r\n```release-note\r\nazure: add PrimaryAvailabilitySet to config, only use nodes in that set in the loadbalancer pool\r\n```\r\n\r\nCC: @brendandburns, @anhowe","distinct":false,"url":"https://api.github.com/repos/mbohlool/kubernetes/commits/3b787c9b3d12d2cae3db99939f7f5b755c59103c"}]}
{"actor":{"display_login":"mbohlool"}}