{"push_id":1375922163,"size":1000,"distinct_size":2631,"ref":"refs/heads/resource_type","head":"36d1db3f42f98e7981c190142abc79782c13e937","before":"972bcb04978032ef2abf8ce6bd60a1408542157c","commits":[{"sha":"480bcb97600fa42c9a237adb77f7f4350d40d84a","author":{"name":"Minhan Xia","email":"0c6821469d0d5e8bf5e55ea8934eaa300b4c0705@google.com"},"message":"add UpdateRuntimeConfig interface","distinct":true,"url":"https://api.github.com/repos/jouve/kubernetes/commits/480bcb97600fa42c9a237adb77f7f4350d40d84a"},{"sha":"a0624835ac52578a36100e16c321e3d0a43eb795","author":{"name":"Kubernetes Submit Queue","email":"260061d766fe633e5411cb223defd984f1ece7b6@users.noreply.github.com"},"message":"Merge pull request #34669 from yujuhong/get_netns\n\nAutomatic merge from submit-queue\n\nAllow kuberuntime to get network namespace for not ready sandboxes\n\nKubelet calls TearDownPod to clean up the network resources for a pod sandbox.\r\nTearDownPod relies on GetNetNS to retrieve network namespace, and the current\r\nimplementation makes this impossible for not-ready sandboxes. This change\r\nremoves the unnecessary filter to fix this issue.","distinct":true,"url":"https://api.github.com/repos/jouve/kubernetes/commits/a0624835ac52578a36100e16c321e3d0a43eb795"},{"sha":"b8b7f9ffc0d400a3a346911c4b1c33284768270b","author":{"name":"Kubernetes Submit Queue","email":"260061d766fe633e5411cb223defd984f1ece7b6@users.noreply.github.com"},"message":"Merge pull request #32722 from juanvallejo/jvallejo_return-err-on-oc-get-empty-list\n\nAutomatic merge from submit-queue\n\nreturn warning on empty list result in kubectl get\n\n**Release note**:\r\n```release-note\r\nNONE\r\n```\r\n\r\nThe current default behavior of `kubectl get` is to return an empty\r\noutput when there are no resources to display. This patch improves\r\nusability by returning a warning through stderr in the case of an empty\r\nlist.\r\n\r\n##### Before\r\n`$ kubectl get pods`\r\n  - *empty output*\r\n\r\n##### After\r\n`$ kubectl get pods`\r\n```\r\nThere are no resources to display.\r\n```","distinct":true,"url":"https://api.github.com/repos/jouve/kubernetes/commits/b8b7f9ffc0d400a3a346911c4b1c33284768270b"},{"sha":"523fce990af518c440c4bcdd0e404d2a3a642fd0","author":{"name":"Kubernetes Submit Queue","email":"260061d766fe633e5411cb223defd984f1ece7b6@users.noreply.github.com"},"message":"Merge pull request #32781 from lukaszo/ready_ds\n\nAutomatic merge from submit-queue\n\nAdd ReadyScheduled to DaemonSet status\n\nFixes #25605\r\n\r\ncc @bgrant0607 @mikedanese","distinct":true,"url":"https://api.github.com/repos/jouve/kubernetes/commits/523fce990af518c440c4bcdd0e404d2a3a642fd0"},{"sha":"5eb75e4eb9d8a045e4d9cfbd1ff7bb84ef6d8f36","author":{"name":"Kubernetes Submit Queue","email":"260061d766fe633e5411cb223defd984f1ece7b6@users.noreply.github.com"},"message":"Merge pull request #34421 from chrislovecnm/cassandra-cpu-fix-flake\n\nAutomatic merge from submit-queue\n\nfixing flake test\n\nThis should fix https://github.com/kubernetes/kubernetes/issues/32941  - I do not know what CPU guidelines I should be using, and I have had challenges running the tests in parallel.  Dropping the PR instead of messing around with trying to get testing run correctly.","distinct":true,"url":"https://api.github.com/repos/jouve/kubernetes/commits/5eb75e4eb9d8a045e4d9cfbd1ff7bb84ef6d8f36"},{"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":true,"url":"https://api.github.com/repos/jouve/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":true,"url":"https://api.github.com/repos/jouve/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":true,"url":"https://api.github.com/repos/jouve/kubernetes/commits/3b787c9b3d12d2cae3db99939f7f5b755c59103c"},{"sha":"8b7e9d303c198d99725cb528b0e0df7dbf529cd7","author":{"name":"gmarek","email":"c24e99ac0cd35e68a4926c343d20c58d2ecae733@google.com"},"message":"Handle DeletedFinalStateUnknown in NodeController","distinct":true,"url":"https://api.github.com/repos/jouve/kubernetes/commits/8b7e9d303c198d99725cb528b0e0df7dbf529cd7"},{"sha":"2d3f294e2ddd80c25961beed4dcb4fdd3775530b","author":{"name":"Mik Vyatskov","email":"714823502c74551132d79cd4f17a3753961f101b@google.com"},"message":"Fix ES cluster logging test","distinct":true,"url":"https://api.github.com/repos/jouve/kubernetes/commits/2d3f294e2ddd80c25961beed4dcb4fdd3775530b"},{"sha":"5496d2273349c124854bc75329d5071afb1543d3","author":{"name":"Kubernetes Submit Queue","email":"260061d766fe633e5411cb223defd984f1ece7b6@users.noreply.github.com"},"message":"Merge pull request #34456 from kargakis/revert-29808\n\nAutomatic merge from submit-queue\n\nRevert \"Error out when any RS has more available pods then its spec r…\n\nReverts https://github.com/kubernetes/kubernetes/pull/29808\r\n\r\nThe PR is wrong because we can have more available pods than desired every time we scale down.\r\n\r\n@kubernetes/deployment ptal","distinct":true,"url":"https://api.github.com/repos/jouve/kubernetes/commits/5496d2273349c124854bc75329d5071afb1543d3"},{"sha":"212a26dc95a5fbe314f25a40a982742bc9b2a0c1","author":{"name":"Michail Kargakis","email":"507be340a25d4f31d599588ff525ee75ea514bb9@redhat.com"},"message":"controller: set minReadySeconds in deployment's replica sets\n\n* Estimate available pods for a deployment by using minReadySeconds on\nthe replica set.\n* Stop requeueing deployments on pod events, superseded by following the\nreplica set status.\n* Cleanup redundant deployment utilities","distinct":true,"url":"https://api.github.com/repos/jouve/kubernetes/commits/212a26dc95a5fbe314f25a40a982742bc9b2a0c1"},{"sha":"ca75b476576f991b33ce70eab74d25e74ef2f26d","author":{"name":"Kubernetes Submit Queue","email":"260061d766fe633e5411cb223defd984f1ece7b6@users.noreply.github.com"},"message":"Merge pull request #32555 from pweil-/admission-authorizer\n\nAutomatic merge from submit-queue\n\nWantsAuthorizer admission plugin support\n\nThe next step of PSP admission is to be able to limit the PSPs used based on user information.  To do this the admission plugin would need to make authz checks for the `user.Info` in the request.  This code allows a plugin to request the injection of an authorizer to allow it to make the authz checks.\r\n\r\nNote:  this could be done with a SAR, however since admission is running in the api server using the SAR would incur an extra hop vs using the authorizer directly.\r\n\r\n@deads2k @derekwaynecarr","distinct":true,"url":"https://api.github.com/repos/jouve/kubernetes/commits/ca75b476576f991b33ce70eab74d25e74ef2f26d"},{"sha":"c1986f0fc7eb79ed11a757deab8b618066bdaaf2","author":{"name":"Kubernetes Submit Queue","email":"260061d766fe633e5411cb223defd984f1ece7b6@users.noreply.github.com"},"message":"Merge pull request #34501 from mikedanese/kubeadm-init-cfg\n\nAutomatic merge from submit-queue\n\nkubeadm: allow kubeadm init to read config from file\n\n@kubernetes/sig-cluster-lifecycle","distinct":true,"url":"https://api.github.com/repos/jouve/kubernetes/commits/c1986f0fc7eb79ed11a757deab8b618066bdaaf2"},{"sha":"aa485ce82c3336b0aa70e27e558d2ce12340a4dd","author":{"name":"Kubernetes Submit Queue","email":"260061d766fe633e5411cb223defd984f1ece7b6@users.noreply.github.com"},"message":"Merge pull request #34699 from Crassirostris/es-logging-test-fix\n\nAutomatic merge from submit-queue\n\nFix ES cluster logging test\n\n@piosz \r\n\r\nFixes flakiness of ES cluster logging test.\r\n\r\nFix #34666","distinct":true,"url":"https://api.github.com/repos/jouve/kubernetes/commits/aa485ce82c3336b0aa70e27e558d2ce12340a4dd"},{"sha":"41278b4c6b5f71ac648c190b9bc7269b3f443d33","author":{"name":"gmarek","email":"c24e99ac0cd35e68a4926c343d20c58d2ecae733@google.com"},"message":"Bump log level in case of Node eviction","distinct":true,"url":"https://api.github.com/repos/jouve/kubernetes/commits/41278b4c6b5f71ac648c190b9bc7269b3f443d33"},{"sha":"ceaf0268810aec726addf82a85b98e43bef60d1c","author":{"name":"deads2k","email":"9eea6a26ae0243814229a46d171002f67ac6168a@redhat.com"},"message":"slim down authorization listing interfaces","distinct":true,"url":"https://api.github.com/repos/jouve/kubernetes/commits/ceaf0268810aec726addf82a85b98e43bef60d1c"},{"sha":"2c4e618be10556cab5645ce5795db770d6a6e169","author":{"name":"deads2k","email":"9eea6a26ae0243814229a46d171002f67ac6168a@redhat.com"},"message":"add rbac shared informers","distinct":true,"url":"https://api.github.com/repos/jouve/kubernetes/commits/2c4e618be10556cab5645ce5795db770d6a6e169"},{"sha":"e1638f11a3994db7e04a5e670e8bd929820c9d45","author":{"name":"deads2k","email":"9eea6a26ae0243814229a46d171002f67ac6168a@redhat.com"},"message":"run authorization from a cache","distinct":true,"url":"https://api.github.com/repos/jouve/kubernetes/commits/e1638f11a3994db7e04a5e670e8bd929820c9d45"},{"sha":"1c65d1df86e773ce9e1496163e724fa52a6dd864","author":{"name":"Kubernetes Submit Queue","email":"260061d766fe633e5411cb223defd984f1ece7b6@users.noreply.github.com"},"message":"Merge pull request #34694 from gmarek/deleted_final_state_unknown\n\nAutomatic merge from submit-queue\n\nHandle DeletedFinalStateUnknown in NodeController\n\nFix #34692\r\n\r\n```release-note\r\nFix panic in NodeController caused by receiving DeletedFinalStateUnknown object from the cache.\r\n```\r\n\r\ncc @davidopp","distinct":true,"url":"https://api.github.com/repos/jouve/kubernetes/commits/1c65d1df86e773ce9e1496163e724fa52a6dd864"}]}
{"actor":{"display_login":"jouve"}}