{"push_id":2765756530,"size":13,"distinct_size":13,"ref":"refs/heads/master","head":"94c2c6c8423d722f436305cd67ef515a8800d723","before":"7ac32a4f7a7ecf0030e3628744a7411bb08b6675","commits":[{"sha":"b1ec6da4c749a9e02bbeba42797e8ffe9e0e6f04","author":{"name":"Seth Jennings","email":"527af9e7c640877508ac9f4ddd8647c066bca6c6@redhat.com"},"message":"kubelet: add image-gc low/high validation check","distinct":true,"url":"https://api.github.com/repos/ii/kubernetes/commits/b1ec6da4c749a9e02bbeba42797e8ffe9e0e6f04"},{"sha":"3c1495d0a4765af4c4639671946308f633f50a95","author":{"name":"David Eads","email":"89303f5b3c40c1b24f758e05b147c2160fb869de@redhat.com"},"message":"aggregate admin from edit and view to ensure coverage","distinct":true,"url":"https://api.github.com/repos/ii/kubernetes/commits/3c1495d0a4765af4c4639671946308f633f50a95"},{"sha":"9120557466df086ede14645a1a143b73b5e299fa","author":{"name":"juanvallejo","email":"6958e48e624f5a104bb59b7f2a9871273b0f8975@redhat.com"},"message":"update attach to use external objs","distinct":true,"url":"https://api.github.com/repos/ii/kubernetes/commits/9120557466df086ede14645a1a143b73b5e299fa"},{"sha":"3a3633a32ec83675b63c126932d00390165d3d54","author":{"name":"juanvallejo","email":"6958e48e624f5a104bb59b7f2a9871273b0f8975@redhat.com"},"message":"update logs","distinct":true,"url":"https://api.github.com/repos/ii/kubernetes/commits/3a3633a32ec83675b63c126932d00390165d3d54"},{"sha":"086ed3c6593a5d5cde51544f9f59dc3854f25641","author":{"name":"Joachim Bartosik","email":"b2338692da24d940a94c816d9519525ff4890354@google.com"},"message":"Rename desiredReplicas to expectedDesiredReplicas\n\nNaming fields specifying values expected by test as expected.* is a nice\nconvention to have, lets follow it.","distinct":true,"url":"https://api.github.com/repos/ii/kubernetes/commits/086ed3c6593a5d5cde51544f9f59dc3854f25641"},{"sha":"7681c284f5b1ee3a1e7830c439b67fe3dc7475e5","author":{"name":"Joachim Bartosik","email":"b2338692da24d940a94c816d9519525ff4890354@google.com"},"message":"Remove UpscaleForbiddenWindow\n\nInstead discard metric values for pods that are unready and have never\nbeen ready (they may report misleading values, the original reason for\nintroducing scale up forbidden window).\n\nUse per pod metric when pod is:\n- Ready, or\n- Not ready but creation timestamp and last readiness change are more\n  than 10s apart.\n\nIn the latter case we asume the pod was ready but later became unready.\nWe want to use metrics for such pods because sometimes such pods are\nunready because they were getting too much load.","distinct":true,"url":"https://api.github.com/repos/ii/kubernetes/commits/7681c284f5b1ee3a1e7830c439b67fe3dc7475e5"},{"sha":"8ef369ea2d1f487e46ca90f64dd30111eafafa78","author":{"name":"Joachim Bartosik","email":"b2338692da24d940a94c816d9519525ff4890354@google.com"},"message":"Mark --horizontal-pod-autoscaler-upscale-delay deprecated","distinct":true,"url":"https://api.github.com/repos/ii/kubernetes/commits/8ef369ea2d1f487e46ca90f64dd30111eafafa78"},{"sha":"217a3d890219abf7eb759e9b64c0403c6ee40e2c","author":{"name":"Deep Debroy","email":"7fa9323c42db6a7f539b501bc29c8e3ab3ebf8bb@docker.com"},"message":"Add DynamicProvisioningScheduling support for EBS\n\nSigned-off-by: Deep Debroy <ddebroy@docker.com>","distinct":true,"url":"https://api.github.com/repos/ii/kubernetes/commits/217a3d890219abf7eb759e9b64c0403c6ee40e2c"},{"sha":"22d0ef2a8ef06ee3040d9a3711bac07f815ecef6","author":{"name":"Kubernetes Submit Queue","email":"5239ff46b5e3e621e3f6a652ec59210ae096c8ec@users.noreply.github.com"},"message":"Merge pull request #65730 from ddebroy/ebs-affinity1\n\nAutomatic merge from submit-queue (batch tested with PRs 65730, 66615, 66684, 66519, 66510). 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 DynamicProvisioningScheduling support for EBS\n\n**What this PR does / why we need it**:\r\n\r\nThis PR adds support for the DynamicProvisioningScheduling feature in EBS. With this in place, if VolumeBindingMode: WaitForFirstConsumer is specified in a EBS storageclass and DynamicProvisioningScheduling is enabled, EBS provisioner will use the selected node's LabelZoneFailureDomain as the zone to provision the EBS volume in.\r\n\r\n**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:\r\nFixes #\r\n\r\n**Special notes for your reviewer**:\r\nRelated to #63232\r\n\r\nSample `describe pv` output with NodeAffinity populated:\r\n\r\n```\r\n~$ kubectl describe pv pvc-f9d2138b-7e3e-11e8-a4ea-064124617820\r\nName:              pvc-f9d2138b-7e3e-11e8-a4ea-064124617820\r\nLabels:            failure-domain.beta.kubernetes.io/region=us-west-2\r\n                   failure-domain.beta.kubernetes.io/zone=us-west-2a\r\nAnnotations:       kubernetes.io/createdby=aws-ebs-dynamic-provisioner\r\n                   pv.kubernetes.io/bound-by-controller=yes\r\n                   pv.kubernetes.io/provisioned-by=kubernetes.io/aws-ebs\r\nFinalizers:        [kubernetes.io/pv-protection]\r\nStorageClass:      slow3\r\nStatus:            Bound\r\nClaim:             default/pvc3\r\nReclaim Policy:    Delete\r\nAccess Modes:      RWO\r\nCapacity:          6Gi\r\nNode Affinity:     \r\n  Required Terms:  \r\n    Term 0:        failure-domain.beta.kubernetes.io/zone in [us-west-2a]\r\n                   failure-domain.beta.kubernetes.io/region in [us-west-2]\r\nMessage:           \r\nSource:\r\n    Type:       AWSElasticBlockStore (a Persistent Disk resource in AWS)\r\n    VolumeID:   aws://us-west-2a/vol-0fc1cdae7d10860f6\r\n    FSType:     ext4\r\n    Partition:  0\r\n    ReadOnly:   false\r\nEvents:         <none>\r\n```\r\n\r\n**Release note**:\r\n```release-note\r\nnone\r\n```\r\n\r\n/sig storage\r\n/assign @msau42 @jsafrane","distinct":true,"url":"https://api.github.com/repos/ii/kubernetes/commits/22d0ef2a8ef06ee3040d9a3711bac07f815ecef6"},{"sha":"c32e0e84dadbdf6274aa939fb91fb92213bdc210","author":{"name":"Kubernetes Submit Queue","email":"5239ff46b5e3e621e3f6a652ec59210ae096c8ec@users.noreply.github.com"},"message":"Merge pull request #66615 from jbartosik/cpu-warm-up\n\nAutomatic merge from submit-queue (batch tested with PRs 65730, 66615, 66684, 66519, 66510). 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\nSpeed up HPA reaction to metric changes by removing scale up forbidden window\n\n**What this PR does / why we need it**:\r\nSpeed up HPA reaction to metric changes by removing scale up forbidden window.\r\n\r\nScale up forbidden window was protecting HPA against making decision to scale up based on metrics gathered during pod initialisation (which may be invalid, for example pod may be using a lot of CPU despite not doing any \"actual\" work).\r\n\r\nTo avoid that negative effect only use per pod metrics from pods that are:\r\n- ready (so metrics about them should be valid), or\r\n- unready but creation and last readiness change timestamps are apart more than 10s (pods that have formerly been ready and so metrics are in at least some cases (pod becoming unready because of overload) very useful).\r\n\r\n\r\nThis PR only deals with scale up window. I'll send another PR dealing with scale down window soon.\r\n\r\n**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:\r\n\r\n**Special notes for your reviewer**:\r\n\r\n**Release note**:\r\n```release-note\r\nSpeed up HPA reaction to metric changes by removing scale up forbidden window.\r\n\r\nScale up forbidden window was protecting HPA against making decision to scale up based on metrics gathered during pod initialisation (which may be invalid, for example pod may be using a lot of CPU despite not doing any \"actual\" work).\r\n\r\nTo avoid that negative effect only use per pod metrics from pods that are:\r\n- ready (so metrics about them should be valid), or\r\n- unready but creation and last readiness change timestamps are apart more than 10s (pods that have formerly been ready and so metrics are in at least some cases (pod becoming unready because of overload) very useful).\r\n```","distinct":true,"url":"https://api.github.com/repos/ii/kubernetes/commits/c32e0e84dadbdf6274aa939fb91fb92213bdc210"},{"sha":"695d4fb584e0c68cd2f8d800518bf583f84af22b","author":{"name":"Kubernetes Submit Queue","email":"5239ff46b5e3e621e3f6a652ec59210ae096c8ec@users.noreply.github.com"},"message":"Merge pull request #66684 from deads2k/rbac-01-aggregate\n\nAutomatic merge from submit-queue (batch tested with PRs 65730, 66615, 66684, 66519, 66510). 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\naggregate admin from edit and view to ensure coverage\n\nClusterRole aggregate has worked quite well.  This updates the edit role to be aggregated from a separate edit and view and updates the admin role to aggregated from admin, edit, and view.  This ensures coverage (we previously had unit tests, but that didn't work as people aggregated more powers in) and it makes each role smaller since it only has a diff to consider.\r\n\r\n@kubernetes/sig-auth-pr-reviews \r\n\r\n```release-note\r\nadmin RBAC role now aggregates edit and view.  edit RBAC role now aggregates view. \r\n```","distinct":true,"url":"https://api.github.com/repos/ii/kubernetes/commits/695d4fb584e0c68cd2f8d800518bf583f84af22b"},{"sha":"9c58985a25a7775fbbfb6ec78ea5da3ff329847b","author":{"name":"Kubernetes Submit Queue","email":"5239ff46b5e3e621e3f6a652ec59210ae096c8ec@users.noreply.github.com"},"message":"Merge pull request #66519 from juanvallejo/jvallejo/switch-attch-externals\n\nAutomatic merge from submit-queue (batch tested with PRs 65730, 66615, 66684, 66519, 66510). 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\nupdate attach to use external objs\n\n**Release note**:\r\n```release-note\r\nNONE\r\n```\r\n\r\nUpdates attach command to use external versions.\r\n\r\ncc @deads2k @soltysh","distinct":true,"url":"https://api.github.com/repos/ii/kubernetes/commits/9c58985a25a7775fbbfb6ec78ea5da3ff329847b"},{"sha":"94c2c6c8423d722f436305cd67ef515a8800d723","author":{"name":"Kubernetes Submit Queue","email":"5239ff46b5e3e621e3f6a652ec59210ae096c8ec@users.noreply.github.com"},"message":"Merge pull request #66510 from sjenning/add-image-gc-validation\n\nAutomatic merge from submit-queue (batch tested with PRs 65730, 66615, 66684, 66519, 66510). 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\nkubelet: add image-gc low/high validation check\n\nCurrently, there is no protection against setting the high watermark <= the low watermark for image GC\r\n\r\nThis PR adds a validation rule for that.\r\n\r\n@smarterclayton","distinct":true,"url":"https://api.github.com/repos/ii/kubernetes/commits/94c2c6c8423d722f436305cd67ef515a8800d723"}]}
{"actor":{"display_login":"hh"}}