- 11 May, 2017 1 commit
-
-
yaxinlx authored
receiver side. fix https://github.com/kubernetes/kubernetes/issues/45215 delete the channel close line change the event channel element type to struct{} go fmt eventCh channel is not essential to be buffered
-
- 03 May, 2017 18 commits
-
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 45272, 45115) initial types for TPRs This pull starts creating the types described by https://github.com/kubernetes/community/blob/master/contributors/design-proposals/thirdpartyresources.md . In the initial pull different names were suggested. I've started this pull with `CustomResource.apiextensions.k8s.io`. The structure begins as a separate API server to facilitate rapid prototyping and experimentation, but the end result will be added to the end of the `kube-apiserver` chain as described in https://github.com/kubernetes/community/blob/master/sig-api-machinery/api-extensions-position-statement.md . Because it is separate to start (not included in any default server), I don't think we need a perfect name, but I'd like to be close. @kubernetes/sig-api-machinery-misc @enisoc @smarterclayton @erictune
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 45272, 45115) apimachinery: make explicit that meta.KindToResource is only a guess All non-test code using `KindToResource` is suspicious and should be fixed with a real RESTMapper.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add wait for federated service deletion Fixes the flaky kubectl tests https://github.com/kubernetes/kubernetes/pull/44987#issuecomment-298790335, https://github.com/kubernetes/kubernetes/issues/45264 service deletion is not instantaneous in federation. The fix is same as https://github.com/kubernetes/kubernetes/pull/42674. We need the fix now for services since we recently fixed federation service controller so that it runs successfully now. cc @shashidharatd
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 45005, 43053) kubelet: fix sandbox garbage collection **What this PR does / why we need it**: Currently, kuberuntime garbage collection can't distinguish just-created sandboxes from failed sandboxes. Especially when the time from sandbox creation to ready is longer than GC's minAge. In such cases, those sandboxes may be garbage collected early before they are ready. This PR removes `sandboxMinGCAge` and only garbage collect sandboxes when * they are containing no containers at all * and not the latest sandbox if it is belonging to an existing pod. **Which issue this PR fixes** Fixes #42856. **Release note**: ```release-note NONE ``` cc @yujuhong @Random-Liu
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 45005, 43053) [Federation]Fix e2e_federation: pass clusterIngress out None
-
Dr. Stefan Schimanski authored
-
Dr. Stefan Schimanski authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 45013, 45166) CRI: remove PodSandboxStatus.Linux.Namespaces.Network **What this PR does / why we need it**: PodSandboxStatus.Linux.Namespaces.Network is not used, so this PR removes it from CRI. **Which issue this PR fixes** Closes: #44972 **Special notes for your reviewer**: **Release note**: ```release-note Remove PodSandboxStatus.Linux.Namespaces.Network from CRI. ``` /assign @Random-Liu @yujuhong
-
Pengfei Ni authored
-
Pengfei Ni authored
Sandboxes are garbage collected only when they are containing no containers at all and not the latest sandbox if it is belonging to an existing pod.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add cinder volume examples I can not find cinder examples,add in packages examples/volume and examples/persistent-volume-provisioning **Release note**: ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue kubelet/get-pods-from-path: correct description of implemention **What this PR does / why we need it**: I find this description does not follow the current implementation, it should be describe like this according to my understanding of the source code. -
nikhiljindal authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 45219, 45246) Fixed misspelled http URL in the cluster-dns example **What this PR does / why we need it**: Fixes wrong http URL in the examples/cluster-dns. **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**: none **Release note**: none
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix golint verify error I don't know why CI pass the hack/verify-golint.sh test. But in my environment I get this: > staging/src/k8s.io/client-go/util/workqueue/queue_test.go is in package workqueue_test, not workqueue Errors from golint: test/integration/apiserver/apiserver_test.go:102:13: should omit type string from declaration of var cascDel; it will be inferred from the right-hand side Please fix the above errors. You can test via "golint" and commit the result. !!! Error in hack/verify-golint.sh:98 Error in hack/verify-golint.sh:98. 'false' exited with status 1 Call stack: 1: hack/verify-golint.sh:98 main(...) Exiting with status 1 This change fix this err in my environment. **Release note**: ```NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue CHANGELOG.md: update outdated link I am not sure that if the file was generated automatically. But I find some links were outdated. Release note: NONE
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Clean up code in dockertools Move functions and sub packages to dockershim. Part of #43234.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue cleancode:util.go cleancode, the modification point make code clean and light
-
- 02 May, 2017 21 commits
-
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 45120, 45243) skip integration test when run make bazel-test we should opt for a seperate target for integration tests. This is breaking @deads2k who is trying to add an integration test in staging.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Also upload debs to bin/$OS/$ARCH **What this PR does / why we need it**: the bazel-built debs are used by the kubeadm e2e tests, so upload them too. https://github.com/kubernetes/kubernetes/pull/44591#issuecomment-298084453 /assign @pipejakob /cc @mikedanese @spxtr **Release note**: ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 45125, 45242) skip procfs-dependent metrics test if not on linux **What this PR does / why we need it**: #40774 removed build tags on integration tests, which uncovered the fact that a test in `test/integration/metrics` relies on `procfs`. This PR follows the convention used in `pkg/util/procfs` to gate the test on `runtime.GOOS` **Release note**: ```release-note NONE ``` /cc @kubernetes/sig-testing-pr-reviews
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 45125, 45242) Update labels.yaml with sig labels **What this PR does / why we need it**: Updates labels.yaml to reflect the state of labels in this repo. Consumed by https://github.com/kubernetes/test-infra/blob/master/mungegithub/mungers/check-labels.go to ensure these labels continue to exist. **Release note**: ```release-note NONE ```
-
Piotr Siwczak authored
-
Mike Danese authored
we should opt for a seperate target for integration tests.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 45239, 45230) Create a single CA for both client and server certs **What this PR does / why we need it**: The following test: "Certificates API [It] should support building a client with a CSR" fails with local-up-cluster, but works in the existing CI jobs. This is because the other CI jobs use a single CA cert while local-up-cluster can use 2 different sets of CA(s). We need a way to mimic the other CI jobs (or alternatively change everything to have separate CA's). Just updating local-up-cluster with a flag seems to be the easy route. **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 NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 45239, 45230) Update bazel build to dockerize cloud-controller-manager **What this PR does / why we need it**: followup to #45154. Also added a comment so that hopefully this sort of followup isn't needed again. :) **Release note**: ```release-note NONE ``` /assign @mikedanese @luxas
-
Aaron Crickenberger authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 40544, 44338, 45225) [Federation]Update event type Use EventTypeWarning instead of EventTypeNormal when get failure Left behind after pr #40296
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 40544, 44338, 45225) Use ObjectGetter Interface instead of clientset.Interface for leaderelection pkg **What this PR does / why we need it**: We plan to reuse leaderelection pkg to add leader election function to federation controller manager, but the current implementation uses kubernetes clientset.Interface and federation clientset does not satisfy all the interface methods. It would be better if the leaderelection package use rest.Interface which is also supported by federation clientset. This pr is to refactor leaderelection pkg to use rest.Interface instead of clientset.Interface **Special notes for your reviewer**: This is a sub-task of bigger work to add leader election to federation controller manager as documented in #44283 **Release note**: ``` NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fixes broken link in PodSpec The PodSpec reference to NodeSelector misses the `.md` extension in the file. **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 # **Special notes for your reviewer**: **Release note**: ```release-note ```
-
Jeff Grafton authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 45227, 43003, 45231) kubeadm: move preflight kubelet check **What this PR does / why we need it**: If you passed the `--skip-preflight-checks` to kubeadm, it would still try to start up the kubelet, which is part of preflight checks. This was causing issues for test-cmds. Now, passing `--skip-preflight-checks` will skip over the kubelet check. **Special notes for your reviewer**: /cc @luxas @deads2k **Release note**: ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 45227, 43003, 45231) separate discovery from the apiserver This decouples the API discovery handlers from the core API server code. It separates the code into a new package and clarifies interfaces with existing TPR code. @kubernetes/sig-api-machinery-pr-reviews
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix hollow proxy to watch services and endpoints Ref #34727
-
Davanum Srinivas authored
The following test: "Certificates API [It] should support building a client with a CSR" fails with local-up-cluster, but works in the existing CI jobs. This is because the other CI jobs use a single CA cert while local-up-cluster can use 2 different sets of CA(s). We need a way to mimic the other CI jobs (or alternatively change everything to have separate CA's). Just updating local-up-cluster with a flag seems to be the easy route.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 45100, 45152, 42513, 44796, 45222) apiserver: split endpoint tests from client-go Use the example apigroup and create its own scheme. Fixes https://github.com/kubernetes/kubernetes/issues/45209.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 45100, 45152, 42513, 44796, 45222) add subresource support to kube auth can-i Eg: kubectl auth can-i get pods --sub-resource=log **Release note**: ```release-note ``` -
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 45100, 45152, 42513, 44796, 45222) [Federation] Generate the secret name in kubefed join. Addresses part of #42324. A follow-up PR will address annotating Federation resources. ```release-note Remove the `--secret-name` flag from `kubefed join`, instead generating the secret name arbitrarily. ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 45100, 45152, 42513, 44796, 45222) Added InterPodAffinity unit test case with Namespace. **What this PR does / why we need it**: Added InterPodAffinity unit test case with Namespace: unit test case for #45098 **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # N/A **Release note**: ```release-note-none ```
-