1. 13 Dec, 2017 1 commit
    • Anthony Yeh's avatar
      gce/upgrade.sh: Prompt if etcd version is unspecified. · bbcf59bd
      Anthony Yeh authored
      We shouldn't upgrade etcd without first warning the user that some etcd
      version transitions can't be undone. We don't know what version the user
      currently has, so we require either an explicit version and image, or an
      interactive acknowledgement of this caveat.
      
      This is modeled after the STORAGE_MEDIA_TYPE prompt just above.
      bbcf59bd
  2. 12 Dec, 2017 12 commits
  3. 11 Dec, 2017 8 commits
  4. 09 Dec, 2017 2 commits
  5. 08 Dec, 2017 6 commits
  6. 07 Dec, 2017 10 commits
  7. 06 Dec, 2017 1 commit
    • Kubernetes Submit Queue's avatar
      Merge pull request #56643 from dashpole/fix_coreos_disk_test · 88db9a75
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue. 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>.
      
      [Test Fix] Make requirements less precise for disk eviction test
      
      **What this PR does / why we need it**:
      Makes the local storage eviction test require less precision.  On coreos and other OS distributions which report the actual disk usage, rather than apparent, an empty file can consume disk space.
      Since the test creates 299 files (each containing 1Mb of data), the extra 4kb disk space reported by each file causes the test in its current form to fail, because it exceeds the 300Mb limit. (4kb * 299 > 1 Mb).
      This change makes the test only create 297 files, which will ensure that small differences in distributions like this do not cause the test to fail.
      
      This behavior was actually meant to be tested in the `LocalStorageCapacityIsolationEviction` test, but was omitted.  I have added a test case to that test as well.
      
      **Which issue(s) this PR fixes**:
      Fixes #56234
      
      ```release-note
      NONE
      ```
      /sig node
      /priority critical-urgent
      /kind bug
      
      As this is a testing only change, my hope is to include it in the 1.9 release.
      /assign @dchen1107 
      /assign @rphillips
      88db9a75