1. 11 Jul, 2016 8 commits
    • k8s-merge-robot's avatar
      Merge pull request #28684 from kargakis/deployment-controller-updates · 39bfa168
      k8s-merge-robot authored
      Automatic merge from submit-queue
      
      Deployment controller updates
      
      @kubernetes/deployment @deads2k PTAL
      39bfa168
    • k8s-merge-robot's avatar
      Merge pull request #28704 from dims/fix-issue-11747 · 0a6561f5
      k8s-merge-robot authored
      Automatic merge from submit-queue
      
      E2E test for kubectl replace
      0a6561f5
    • k8s-merge-robot's avatar
      Merge pull request #28697 from Random-Liu/fix-kube-proxy-panic · 6462f822
      k8s-merge-robot authored
      Automatic merge from submit-queue
      
      Prevent kube-proxy from panicing when sysfs is mounted as read-only.
      
      Fixes https://github.com/kubernetes/kubernetes/issues/25543.
      
      This PR:
      * Checks the permission of sysfs before setting conntrack hashsize, and returns an error "readOnlySysFSError" if sysfs is readonly. As I know, this is the only place we need write permission to sysfs, CMIIW.
      * Update a new node condition 'RuntimeUnhealthy' with specific reason, message and hit to the administrator about the remediation.
      
      I think this should be an acceptable fix for now.
      Node problem detector is designed to integrate with different problem daemons, but **the main logic is in the problem detection phase**. After the problem is detected, what node problem detector does is also simply updating a node condition.
      
      If we let kube-proxy pass the problem to node problem detector and let node problem detector update the node condition. It looks like an unnecessary hop. The logic in kube-proxy won't be different from this PR, but node problem detector will have to open an unsafe door to other pods because the lack of authentication mechanism.
      
      It is a bit hard to test this PR, because we don't really have a bad docker in hand. I can only manually test it:
      * If I manually change the code to let it return `"readOnlySysFSError`, the node condition will be updated:
      ```
        NetworkUnavailable 	False 	Mon, 01 Jan 0001 00:00:00 +0000 	Fri, 08 Jul 2016 01:36:41 -0700 	RouteCreated 			RouteController created a route
        OutOfDisk 		False 	Fri, 08 Jul 2016 01:37:36 -0700 	Fri, 08 Jul 2016 01:34:49 -0700 	KubeletHasSufficientDisk 	kubelet has sufficient disk space available
        MemoryPressure 	False 	Fri, 08 Jul 2016 01:37:36 -0700 	Fri, 08 Jul 2016 01:34:49 -0700 	KubeletHasSufficientMemory 	kubelet has sufficient memory available
        Ready 		True 	Fri, 08 Jul 2016 01:37:36 -0700 	Fri, 08 Jul 2016 01:35:26 -0700 	KubeletReady 			kubelet is posting ready status. WARNING: CPU hardcapping unsupported
        RuntimeUnhealthy 	True 	Fri, 08 Jul 2016 01:35:31 -0700 	Fri, 08 Jul 2016 01:35:31 -0700 	ReadOnlySysFS 			Docker unexpectedly mounts sysfs as read-only for privileged container (docker issue #24000). This causes the critical system components of Kubernetes not properly working. To remedy this please restart the docker daemon.
        KernelDeadlock 	False 	Fri, 08 Jul 2016 01:37:39 -0700 	Fri, 08 Jul 2016 01:35:34 -0700 	KernelHasNoDeadlock 		kernel has no deadlock
      Addresses:		10.240.0.3,104.155.176.101
      ```
      * If not, the node condition `RuntimeUnhealthy` won't appear.
      * If I run the permission checking code in a unprivileged container, it did return `readOnlySysFSError`.
      
      I'm not sure whether we want to mark the node as `Unscheduable` when this happened, which only needs few lines change. I can do that if we think we should.
      
      I'll add some unit test if we think this fix is acceptable.
      
      /cc @bprashanth @dchen1107 @matchstick @thockin @alex-mohr 
      
      Mark P1 to match the original issue.
      [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/.github/PULL_REQUEST_TEMPLATE.md?pixel)]()
      6462f822
    • k8s-merge-robot's avatar
      Merge pull request #28570 from kevinjkj/kevinjkj-patch-3 · d6e84cc2
      k8s-merge-robot authored
      Automatic merge from submit-queue
      
      Optimizing the processing flow of HandlePodAdditions and canAdmitPod …
      
      Optimizing the processing flow of HandlePodAdditions and canAdmitPod methods. If the following loop body in canAdmitPod method is removed, the detection speed can be improved, and the change is very small.
      ------
      otherPods := []*api.Pod{}
      	for _, p := range pods {
      		if p != pod {
      			otherPods = append(otherPods, p)
      		}
      	}
      ------
      d6e84cc2
    • Random-Liu's avatar
      Prevent kube-proxy from panicing when sysfs is mounted as read-only. · 42468532
      Random-Liu authored
      Send a node event when this happens and hint to the administrator
      about the remediation.
      42468532
    • k8s-merge-robot's avatar
      Merge pull request #28672 from ping035627/ping035627-patch-0708 · 1c535008
      k8s-merge-robot authored
      Automatic merge from submit-queue
      
      Inspect the nodeInfo first for CheckServiceAffinity in predicates.go
      
      Suggest to inspect the nodeInfo first for CheckServiceAffinity in predicates.go. When nodeInfo.Node() is nil, return quickly.
      1c535008
    • Kevin Wang's avatar
      Optimizing the processing flow of HandlePodAdditions and canAdmitPod methods. · 09344c1f
      Kevin Wang authored
      Signed-off-by: 's avatarKevin Wang <wang.kanghua@zte.com.cn>
      
      change the note for the canAdmitPod method.
      Signed-off-by: 's avatarKevin Wang <wang.kanghua@zte.com.cn>
      
      gofmt kubelet.go
      Signed-off-by: 's avatarKevin Wang <wang.kanghua@zte.com.cn>
      09344c1f
    • PingWang's avatar
      Update CheckServiceAffinity in predicates.go · 4fde2ff3
      PingWang authored
      Signed-off-by: 's avatarPingWang <wang.ping5@zte.com.cn>
      
      gofmt -s -w
      Signed-off-by: 's avatarPingWang <wang.ping5@zte.com.cn>
      4fde2ff3
  2. 10 Jul, 2016 5 commits
    • k8s-merge-robot's avatar
      Merge pull request #22217 from davidopp/rescheduling · 710374b6
      k8s-merge-robot authored
      Automatic merge from submit-queue
      
      [WIP/RFC] Rescheduling in Kubernetes design proposal
      
      Proposal by @bgrant0607 and @davidopp (and inspired by years of discussion and experience from folks who worked on Borg and Omega).
      
      This doc is a proposal for a set of inter-related concepts related to "rescheduling" -- that is, "moving" an already-running pod to a new node in order to improve where it is running. (Specific concepts discussed are priority, preemption, disruption budget, quota, `/evict` subresource, and rescheduler.)
      
      Feedback on the proposal is very welcome. For now, please stick to comments about the design, not spelling, punctuation, grammar, broken links, etc., so we can keep the doc uncluttered enough to make it easy for folks to comment on the more important things. 
      
      ref/ #22054 #18724 #19080 #12611 #20699 #17393 #12140 #22212
      
      @HaiyangDING @mqliang @derekwaynecarr @kubernetes/sig-scheduling @kubernetes/huawei @timothysc @mml @dchen1107
      710374b6
    • David Oppenheimer's avatar
      b77e3929
    • k8s-merge-robot's avatar
      Merge pull request #26315 from dims/fix-issue-26303 · 00d00cda
      k8s-merge-robot authored
      Automatic merge from submit-queue
      
      Support --all-namespaces in kubectl describe
      
      
      Work In Progress :)
      
      Fixes #26303
      00d00cda
    • Eric Tune's avatar
      Merge pull request #28564 from erictune/foof · b983849a
      Eric Tune authored
      Update changelog.
      b983849a
    • k8s-merge-robot's avatar
      Merge pull request #28670 from wojtek-t/scheduler_metadata · a261776f
      k8s-merge-robot authored
      Automatic merge from submit-queue
      
      Add meta field to predicate signature to avoid computing the same things multiple times
      
      This PR only uses it to avoid computing QOS of a pod for every node from scratch.
      
      Ref #28590
      a261776f
  3. 09 Jul, 2016 16 commits
  4. 08 Jul, 2016 11 commits