{"push_id":2043262624,"size":8,"distinct_size":8,"ref":"refs/heads/master","head":"494be59fda71f466590766d2b0313718e3498997","before":"02187a0ea7c786ae76c831e1d6ad0e74f8a5c683","commits":[{"sha":"b45a406aca6995a1da4856d6d02e5dc3d23cd495","author":{"name":"Dane LeBlanc","email":"6b48fc52b02860b4cd95cc6f214afcdcc2b2e300@cisco.com"},"message":"Fix kube-proxy to use proper iptables commands for IPv6 operation\n\nFor iptables save and restore operations, kube-proxy currently uses\nthe IPv4 versions of the iptables save and restore utilities\n(iptables-save and iptables-restore, respectively). For IPv6 operation,\nthe IPv6 versions of these utilities needs to be used\n(ip6tables-save and ip6tables-restore, respectively).\n\nBoth this change and PR #48551 are needed to get Kubernetes services\nto work in an IPv6-only Kubernetes cluster (along with setting\n'--bind-address ::0' on the kube-proxy command line. This change\nwas alluded to in a discussion on services for issue #1443.\n\nfixes #50474","distinct":true,"url":"https://api.github.com/repos/ii/kubernetes/commits/b45a406aca6995a1da4856d6d02e5dc3d23cd495"},{"sha":"326754eea4f4b49d2514e40ca7c3edee72f07415","author":{"name":"André Martins","email":"89124ad1f812d0391aa6b73008eaa35fadaaee87@gmail.com"},"message":"Removed the IPv6 prefix size limit for cluster-cidr\n\nSigned-off-by: André Martins <aanm90@gmail.com>","distinct":true,"url":"https://api.github.com/repos/ii/kubernetes/commits/326754eea4f4b49d2514e40ca7c3edee72f07415"},{"sha":"2e362ea1421c6f777fa0bf9f6a9b8e6cf3d2f54a","author":{"name":"Joe Betz","email":"aef3ecef5922b288c4e67034879e0f0bbe3e23b7@google.com"},"message":"Add 'ETCD_DOCKER_REPOSITORY' environment variable override to 'cluster/' scripts.\n\nThis allows the etcd docker registry that is currently hard coded to\n`gcr.io/google_containers/etcd` in the `etcd.manifest` template to be\noverridden.  This can be used to test new versions of etcd with\nkubernetes that have not yet been published to\n`gcr.io/google_containers/etcd` and also enables cluster operators to\nmanage the etcd images used by their cluster in an internal\nrepository.","distinct":true,"url":"https://api.github.com/repos/ii/kubernetes/commits/2e362ea1421c6f777fa0bf9f6a9b8e6cf3d2f54a"},{"sha":"80f57b7df7cefdefa60d5c543d1767d5ac157818","author":{"name":"Zihong Zheng","email":"bd05021885addcd6e2224af49aa1a960efb6e19b@google.com"},"message":"GCE kube-down: Delete all remaining firewall rules when KUBE_DELETE_NETWORK is set","distinct":true,"url":"https://api.github.com/repos/ii/kubernetes/commits/80f57b7df7cefdefa60d5c543d1767d5ac157818"},{"sha":"ee567538f0fc74198679a099c03512531ae94e5f","author":{"name":"Kubernetes Submit Queue","email":"260061d766fe633e5411cb223defd984f1ece7b6@users.noreply.github.com"},"message":"Merge pull request #52520 from jpbetz/etcd_docker_repository\n\nAutomatic merge from submit-queue (batch tested with PRs 52520, 52033, 53626, 50478). If you want to cherry-pick this change to another branch, please follow the instructions <a href=\"https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md\">here</a>.\n\nAdd 'ETCD_DOCKER_REPOSITORY' env var override to 'cluster/' scripts.\n\n**What this PR does / why we need it**:\r\n\r\nThis allows the etcd docker registry that is currently hard coded to `gcr.io/google_containers/etcd` in the `etcd.manifest` template to be overridden.  This can be used to test new versions of etcd with kubernetes that have not yet been published to `gcr.io/google_containers/etcd` and also enables cluster operators that use the 'cluster/' scripts to manage the etcd images used by their cluster in an internal repository.\r\n\r\nExample usage:\r\n\r\n```\r\n$ export ETCD_DOCKER_REPOSITORY=gcr.io/jpbetz-public-images/etcd \r\n$ export ETCD_IMAGE=3.0.17 \r\n$ cluster/kube-up.sh\r\n...\r\n$ gcloud compute ssh kubernetes-master\r\n~ $ sudo cat /etc/kubernetes/manifests/etcd.manifest\r\n{\r\n\"apiVersion\": \"v1\",\r\n\"kind\": \"Pod\",\r\n\"metadata\": {\r\n  \"name\":\"etcd-server\",\r\n  ...\r\n},\r\n\"spec\":{\r\n\"hostNetwork\": true,\r\n\"containers\":[\r\n    {\r\n    \"name\": \"etcd-container\",\r\n    \"image\": \"gcr.io/jpbetz-public-images/etcd:3.0.17\",\r\n...\r\n```\r\n**Release note**:\r\n```release-note\r\n```","distinct":true,"url":"https://api.github.com/repos/ii/kubernetes/commits/ee567538f0fc74198679a099c03512531ae94e5f"},{"sha":"7f418a011f7725b84cf51b9a4a3d59cd096a9590","author":{"name":"Kubernetes Submit Queue","email":"260061d766fe633e5411cb223defd984f1ece7b6@users.noreply.github.com"},"message":"Merge pull request #52033 from aanm/50395-removing-max-prefix-length-ipv6-cidr\n\nAutomatic merge from submit-queue (batch tested with PRs 52520, 52033, 53626, 50478). If you want to cherry-pick this change to another branch, please follow the instructions <a href=\"https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md\">here</a>.\n\nRemoved the IPv6 prefix size limit for cluster-cidr\n\nFixes #50395\r\n\r\n/sig network\r\n/area ipv6\r\n\r\ncc @rpothier","distinct":true,"url":"https://api.github.com/repos/ii/kubernetes/commits/7f418a011f7725b84cf51b9a4a3d59cd096a9590"},{"sha":"02b6037365bf106bd6ae8ed0412537ebd749ae23","author":{"name":"Kubernetes Submit Queue","email":"260061d766fe633e5411cb223defd984f1ece7b6@users.noreply.github.com"},"message":"Merge pull request #53626 from MrHohn/gce-delete-network-fw\n\nAutomatic merge from submit-queue (batch tested with PRs 52520, 52033, 53626, 50478). If you want to cherry-pick this change to another branch, please follow the instructions <a href=\"https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md\">here</a>.\n\nGCE kube-down: Delete all remaining firewall rules when DELETE_NETWORK is set\n\n**What this PR does / why we need it**: From https://github.com/kubernetes/kubernetes/issues/52347#issuecomment-335245693, we think it'd be reasonable to cleanup firewall resources as well during GCE kube-down.\r\n\r\n**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #NONE\r\n\r\n**Special notes for your reviewer**:\r\n/assign @shyamjvs @bowei \r\n\r\n**Release note**:\r\n\r\n```release-note\r\nNONE\r\n```","distinct":true,"url":"https://api.github.com/repos/ii/kubernetes/commits/02b6037365bf106bd6ae8ed0412537ebd749ae23"},{"sha":"494be59fda71f466590766d2b0313718e3498997","author":{"name":"Kubernetes Submit Queue","email":"260061d766fe633e5411cb223defd984f1ece7b6@users.noreply.github.com"},"message":"Merge pull request #50478 from leblancd/v6_iptables_cmds\n\nAutomatic merge from submit-queue (batch tested with PRs 52520, 52033, 53626, 50478). If you want to cherry-pick this change to another branch, please follow the instructions <a href=\"https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md\">here</a>.\n\nFix kube-proxy to use proper iptables commands for IPv6 operation\n\nFor iptables save and restore operations, kube-proxy currently uses\r\nthe IPv4 versions of the iptables save and restore utilities\r\n(iptables-save and iptables-restore, respectively). For IPv6 operation,\r\nthe IPv6 versions of these utilities need to be used\r\n(ip6tables-save and ip6tables-restore, respectively).\r\n\r\nBoth this change and PR #48551 are needed to get Kubernetes services\r\nto work in an IPv6-only Kubernetes cluster (along with setting\r\n'--bind-address ::0' on the kube-proxy command line. This change\r\nwas alluded to in a discussion on services for issue #1443.\r\n\r\nfixes #50474\r\n\r\n\r\n\r\n**What this PR does / why we need it**:\r\nThis change modifies kube-proxy so that it uses the proper commands for iptables save and\r\niptables restore for IPv6 operation. Currently kube-proxy uses 'iptables-save' and 'iptables-restore'\r\nregardless of whether it is being used in IPv4 or IPv6 mode. This change fixes kube-proxy so\r\nthat it uses 'ip6tables-save' and 'ip6tables-restore' commands when kube-proxy is being run\r\nin IPv6 mode.\r\n\r\n**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #50474\r\n\r\n**Special notes for your reviewer**:\r\n\r\n**Release note**:\r\n\r\n```release-note NONE\r\n```","distinct":true,"url":"https://api.github.com/repos/ii/kubernetes/commits/494be59fda71f466590766d2b0313718e3498997"}]}
{"actor":{"display_login":"hh"}}