1. 06 Sep, 2017 1 commit
    • Kubernetes Submit Queue's avatar
      Merge pull request #51186 from dixudx/fix_delete_uninitialized_resources · ee4e4a54
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue (batch tested with PRs 51186, 50350, 51751, 51645, 51837)
      
      fix bug on kubectl deleting uninitialized resources
      
      **What this PR does / why we need it**:
      
      **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #51185
      
      **Special notes for your reviewer**:
      /assign @caesarxuchao @ahmetb 
      
      **Release note**:
      
      ```release-note
      fix bug on kubectl deleting uninitialized resources
      ```
      ee4e4a54
  2. 05 Sep, 2017 34 commits
  3. 04 Sep, 2017 5 commits
    • Kubernetes Submit Queue's avatar
      Merge pull request #47367 from derekwaynecarr/event-spam · 870406be
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue
      
      Add client side event spam filtering
      
      **What this PR does / why we need it**:
      Add client side event spam filtering to stop excessive traffic to api-server from internal cluster components.
      
      this pr defines a per source+object event budget of 25 burst with refill of 1 every 5 minutes.
      
      i tested this pr on the following scenarios:
      
      **Scenario 1: Node with 50 crash-looping pods**
      ```
      $ create 50 crash-looping pods on a single node
      $ kubectl run bad --image=busybox --replicas=50 --command -- derekisbad
      ```
      Before:
      * POST events with peak of 1.7 per second, long-tail: 0.2 per second
      * PATCH events with peak of 5 per second, long-tail: 5 per second
      
      After:
      * POST events with peak of 1.7 per second, long-tail: 0.2 per second
      * PATCH events with peak of 3.6 per second, long-tail: 0.2 per second
      
      Observation:
      * https://github.com/kubernetes/kubernetes/pull/47462 capped the number of total events in the long-tail as expected, but did nothing to improve total spam of master.
      
      **Scenario 2: replication controller limited by quota**
      ```
      $ kubectl create quota my-quota --hard=pods=1
      $ kubectl run nginx --image=nginx --replicas=50
      ```
      Before:
      * POST events not relevant as aggregation worked well here.
      * PATCH events with peak and long-tail of 13.6 per second
      
      After:
      * POST events not relevant as aggregation worked well here.
      * PATCH events with peak: .35 per second, and long-tail of 0
      
      **Which issue this PR fixes**
      fixes https://github.com/kubernetes/kubernetes/issues/47366
      
      **Special notes for your reviewer**:
      this was a significant problem in a kube 1.5 cluster we are running where events were co-located in a single etcd.  this cluster was normal to have larger numbers of unhealty pods as well as denial by quota.
      
      **Release note**:
      ```release-note
      add support for client-side spam filtering of events
      ```
      870406be
    • Kubernetes Submit Queue's avatar
      Merge pull request #51904 from liggitt/registry-approver · 1d3c6c01
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue
      
      Add liggitt to registry approvers
      
      ~50 commits to this subtree, and changes to pkg/api, apimachinery, and apiserver (already in approvers list) usually involve corresponding changes here
      
      /assign @smarterclayton
      /assign @lavalamp
      /assign @wojtek-t
      1d3c6c01
    • Kubernetes Submit Queue's avatar
      Merge pull request #51913 from crassirostris/sd-logging-e2e-system-logs-filter · cb3bb111
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue
      
      Fix Stackdriver Logging tests for large clusters
      
      Fixes https://github.com/kubernetes/kubernetes/issues/51700
      
      Due to the limit on the length of the filter, filtering out all nodes in the cluster is not possible. Removing the filter shouldn't affect the tests, since the checks are made based on the nodeIds in the cluster that are unique anyway
      cb3bb111
    • Jordan Liggitt's avatar
      5acd5b52
    • Kubernetes Submit Queue's avatar
      Merge pull request #51794 from wojtek-t/fix_migration_script · 16edd13b
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue
      
      Make etcd prefix configurable in migration script
      
      Followup from https://github.com/kubernetes/kubernetes/pull/49629
      
      @jpbetz
      16edd13b