1. 08 Aug, 2016 1 commit
  2. 07 Aug, 2016 7 commits
    • Kubernetes Submit Queue's avatar
      Merge pull request #30136 from m1093782566/master · e19ea41a
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue
      
      remove useless value copy
      
      Copy something to values in parameters won't change them in go. So, remove it to avoid making people confused.
      e19ea41a
    • Kubernetes Submit Queue's avatar
      Merge pull request #30193 from levackt/patch-1 · 18ede140
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue
      
      Update secrets.md
      18ede140
    • Kubernetes Submit Queue's avatar
      Merge pull request #30181 from mikedanese/csr-delete · 148b7488
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue
      
      add delete strategy to certificates registry
      
      So that CSRs can be deleted.
      
      cc @gtank 
      
      ```console
      $ kubectl delete certificatesigningrequest foo
      error: error when deleting "foo": http: server closed connection
      ```
      and on the apiserver:
      ```
      E0806 00:11:53.791039       5 runtime.go:64] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
      /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/util/runtime/runtime.go:70
      /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/util/runtime/runtime.go:63
      /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/util/runtime/runtime.go:49
      /usr/local/go/src/runtime/asm_amd64.s:472
      /usr/local/go/src/runtime/panic.go:443
      /usr/local/go/src/runtime/panic.go:62
      /usr/local/go/src/runtime/sigpanic_unix.go:24
      /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/api/rest/create.go:115
      /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/api/rest/delete.go:50
      /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/registry/generic/registry/store.go:634
      /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/apiserver/resthandler.go:799
      /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/apiserver/resthandler.go:953
      /usr/local/go/src/runtime/asm_amd64.s:1998
      panic: runtime error: invalid memory address or nil pointer dereference [recovered]
              panic: runtime error: invalid memory address or nil pointer dereference
      [signal 0xb code=0x1 addr=0x20 pc=0xa268ee]
      
      goroutine 1161 [running]:
      panic(0x2a00240, 0xc820014070)
              /usr/local/go/src/runtime/panic.go:481 +0x3e6
      k8s.io/kubernetes/pkg/util/runtime.HandleCrash(0xc821ecbef8, 0x1, 0x1)
              /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/util/runtime/runtime.go:56 +0x153
      panic(0x2a00240, 0xc820014070)
              /usr/local/go/src/runtime/panic.go:443 +0x4e9
      k8s.io/kubernetes/pkg/api/rest.objectMetaAndKind(0x0, 0x0, 0x7faf1332ee78, 0xc8220f0600, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
              /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/api/rest/create.go:115 +0x1ee
      k8s.io/kubernetes/pkg/api/rest.BeforeDelete(0x0, 0x0, 0x7faf13188338, 0xc821e218f0, 0x7faf1332ee78, 0xc8220f0600, 0xc821eb11c0, 0x0, 0x0, 0x0)
              /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/api/rest/delete.go:50 +0x94
      k8s.io/kubernetes/pkg/registry/generic/registry.(*Store).Delete(0xc82013c9a0, 0x7faf13188338, 0xc821e218f0, 0xc821e0bdde, 0xa, 0xc821eb11c0, 0x0, 0x0, 0x0, 0x0)
              /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/registry/generic/registry/store.go:634 +0x3b8
      k8s.io/kubernetes/pkg/apiserver.DeleteResource.func1.1(0x0, 0x0, 0x0, 0x0)
              /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/apiserver/resthandler.go:799 +0xa4
      k8s.io/kubernetes/pkg/apiserver.finishRequest.func1(0xc821e081e0, 0xc821eb12c0, 0xc821e08000, 0xc821e0bf80)
              /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/apiserver/resthandler.go:953 +0xd9
      created by k8s.io/kubernetes/pkg/apiserver.finishRequest
              /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/apiserver/resthandler.go:958 +0xf1
      ```
      148b7488
    • Huamin Chen's avatar
      allow a read-only rbd image mounted by multiple pods · 730db45e
      Huamin Chen authored
      Signed-off-by: 's avatarHuamin Chen <hchen@redhat.com>
      730db45e
    • Taariq Levack's avatar
      Update secrets.md · a9389d68
      Taariq Levack authored
      Typo, environment should be prod not pod
      a9389d68
    • Kubernetes Submit Queue's avatar
      Merge pull request #30141 from sttts/sttts-affinity-logic · eb52d55d
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue
      
      e2e flake: real fix of PodAntiAffinity test
      
      The fix in PR https://github.com/kubernetes/kubernetes/pull/30135 was wrong in using a wrong test condition for an already broken test.
      
      ### Summary
      
      The test tries to launch a pod with an anti-affinity annotation, waits 10
      seconds and then checks that it is still pending.
      
      But the anti-affinity annotation does not forbid to launch that pod on just
      another node that does not have the zone label at all.
      
      This commit changes this behavior by labeling two nodes with the zone label
      and then forcing the pod to be launched on one of those two nodes.
      
      **I assume here that a non-existing label is considered as a different label value.**
      
        Fixes #30078
      eb52d55d
    • Kubernetes Submit Queue's avatar
      Merge pull request #28104 from ping035627/ping035627-patch-4 · 711b63e7
      Kubernetes Submit Queue authored
      Automatic merge from submit-queue
      
      SchedulerExtender: add failedPredicateMap in Filter() returns
      
      Fix #25797. modify extender.Filter for adding extenders information to “failedPredicateMap” in findNodesThatFit.
      When all the filtered nodes that passed "predicateFuncs" don’t pass the extenders filter, the failedPredicateMap hasn’t the extenders information, should add it, I think. So when the length of the “filteredNodes.Items” is 0, we can know the integral information. (The length of the “filteredNodes.Items” is 0, may be because the extenders filter failed.)
      711b63e7
  3. 06 Aug, 2016 19 commits
  4. 05 Aug, 2016 13 commits