1. 05 Jul, 2017 12 commits
  2. 04 Jul, 2017 22 commits
  3. 03 Jul, 2017 6 commits
    • Kubernetes Submit Queue's avatar
      Merge pull request #48394 from smarterclayton/must_serialize_if_data_differs · 4ae3b032
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue (batch tested with PRs 48439, 48440, 48394)
      
      GuaranteedUpdate must write if stored data is not canonical
      
      An optimization added to the GuaranteedUpdate loop changed the
      comparison of the current objects serialization against the stored data,
      instead comparing to the in memory object, which defeated the mechanism
      we use to migrate stored data (GET then PUT should update the version stored in etcd if the canonical serialization has changed)
      
      This commit preserves that optimization but correctly verifies the in
      memory serialization against the on disk serialization by fetching the
      latest serialized data. Since most updates are not no-ops, this should
      not regress the performance of the normal path.
      
      Fixes #48393
      
      ```release-note
      When performing a GET then PUT, the kube-apiserver must write the canonical representation of the object to etcd if the current value does not match. That allows external agents to migrate content in etcd from one API version to another, across different storage types, or across varying encryption levels. This fixes a bug introduced in 1.5 where we unintentionally stopped writing the newest data.
      ```
      4ae3b032
    • Kubernetes Submit Queue's avatar
      Merge pull request #48440 from Cynerva/gkk/snap-upgrades-restart-services · e1d9ab20
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue (batch tested with PRs 48439, 48440, 48394)
      
      Fix kubernetes charms not restarting services after snap upgrades
      
      **What this PR does / why we need it**:
      
      This fixes a problem where the Kubernetes charms don't restart services after upgrading snaps. This can cause certain fixes not to be picked up (for example https://github.com/juju-solutions/release/pull/10)
      
      **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #
      
      **Special notes for your reviewer**:
      
      **Release note**:
      
      ```release-note
      Fixed kubernetes charms not restarting services after snap upgrades
      ```
      e1d9ab20
    • Kubernetes Submit Queue's avatar
      Merge pull request #48439 from juju-solutions/bug/namespaces-path · 937369bc
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue (batch tested with PRs 48439, 48440, 48394)
      
      Fix: namespace-create have kubectl in path
      
      **What this PR does / why we need it**: In juju deployed clusters namespace-create action is failing
      
      **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/326
      
      **Special notes for your reviewer**:
      
      **Release note**:
      
      ```Fix: namespace-create action on Juju deployed clusters
      ```
      937369bc
    • George Kraft's avatar
      f0e08818
    • Kubernetes Submit Queue's avatar
      Merge pull request #46949 from xingzhou/typo · c662e1d7
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue
      
      Fixed a comment typo
      
      Typo fix
      
      Fixed #48414 
      
      **Release note**:
      ```
      None
      ```
      c662e1d7
    • Kubernetes Submit Queue's avatar
      Merge pull request #48354 from deads2k/gc-01-deletenever · 74bde7f7
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue (batch tested with PRs 47784, 47793, 48334, 48435, 48354)
      
      allow a deletestrategy to opt-out of GC
      
      Not all resources should be GC-able and we implemented an ignore list to handle this, but at the storage layer they could still set finalizers, they just hung in a stuck state forever.  This updates the strategy to allow a resource to indicate that they shouldn't be GCed.
      
      @kubernetes/sig-api-machinery-misc
      74bde7f7