- 12 Jul, 2016 15 commits
-
-
k8s-merge-robot authored
Automatic merge from submit-queue Move CIDR allocation logic away from nodecontroller.go cc @fgrzadkowski @wojtek-t @mqliang
-
k8s-merge-robot authored
Automatic merge from submit-queue Generates DELETE pod update operations fixes #27105 Generates DELETE pod update operations to make the code and log more intuitive. 1. main refactoring is in `kubelet/config` 2. kubelet will log if it received DELETE, just like other OPs cc @Random-Liu :)
-
gmarek authored
-
k8s-merge-robot authored
Automatic merge from submit-queue Deprecate the term "Ubernetes" Deprecate the term "Ubernetes" in favor of "Cluster Federation" and "Multi-AZ Clusters"
-
Harry Zhang authored
Signed-off-by:Harry Zhang <harryz@hyper.sh> Combine delete with update
-
k8s-merge-robot authored
Automatic merge from submit-queue Add test case to TestPodFitsResources() of scheduler algorithm File "plugin\pkg\scheduler\algorithm\predicates", function "TestPodFitsResources()", line 199, only provide test case "one resource cpu fits but memory not", it should add test case "one resource memory fits but cpu not".
-
k8s-merge-robot authored
Automatic merge from submit-queue Fix path for examples - storage/volume directories changed Added /volume and /storage in a couple of spots. Fixes #27978
-
k8s-merge-robot authored
Automatic merge from submit-queue Return server's representation of pod from framework pod creation functions Since PodInterface.Create returns the server's representation of the pod, which may differ from the api.Pod object passed to Create, we do the same from the framework's pod creation functions. This is useful if e.g. you create pods using Pod.GenerateName rather than Pod.Name, and you still want to refer to pods by name later on (e.g. for deletion). cc @timstclair
-
k8s-merge-robot authored
Automatic merge from submit-queue Proposal: client/server container runtime Ref #25899 #13768 Proposal for client/server container runtime CC @brendandburns @dchen1107 @kubernetes/goog-node @kubernetes/sig-node
-
Davanum Srinivas authored
Fixes #27978
-
k8s-merge-robot authored
Automatic merge from submit-queue close channel to prevent buildup of wait.JitterUntil() <!-- Checklist for submitting a Pull Request Please remove this comment block before submitting. 1. Please read our [contributor guidelines](https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md). 2. See our [developer guide](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md). 3. If you want this PR to automatically close an issue when it is merged, add `fixes #<issue number>` or `fixes #<issue number>, fixes #<issue number>` to close multiple issues (see: https://github.com/blog/1506-closing-issues-via-pull-requests). 4. Follow the instructions for [labeling and writing a release note for this PR](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes) in the block below. --> Trying to look at flake in #26377 by running the test with large counts of runs. It was timing out because a `wait.JitterUntil` goroutine builds up for each of the four tests. So if you ran it a thousand times, you would end up with 4k goroutines spinning in the background. Now I create a channel and close it at the end of each test to prevent a memory leak.
-
k8s-merge-robot authored
Automatic merge from submit-queue bump cni version @mikedanese do you mind take a look and see if I miss anything?
-
Pengfei Ni authored
-
k8s-merge-robot authored
Automatic merge from submit-queue Include inode info in container summary #28719
-
k8s-merge-robot authored
Automatic merge from submit-queue Update godeps libcontainer @vishh PTAL For #27204.
-
- 11 Jul, 2016 25 commits
-
-
k8s-merge-robot authored
Automatic merge from submit-queue Migrate to kuberetes-release-dev []() This turns off the kubernetes-release-dev mirror. #28193 should have shifted all the references over, this should ensure that it's true. Along the way: Modify it so that the equal bucket and mirror is a noop for things like https://github.com/kubernetes/test-infra/pull/244.
-
k8s-merge-robot authored
Automatic merge from submit-queue resource.Builder should not alter error type from server
-
k8s-merge-robot authored
Automatic merge from submit-queue --no-header available now for custom-column Change `CustomColumnsPrinter` to have `noHeader` boolean, also changed `GetPrinter` to receive this bool and pass it through. One test `TestNewColumnPrinterFromSpecWithNoHeaders` added for checking if there is no headers in output for sure fixes #24133
-
Ron Lai authored
-
Minhan Xia authored
-
David McMahon authored
-
Zach Loafman authored
This turns off the kubernetes-release-dev mirror. #28193 should have shifted all the references over, this should ensure that it's true.
-
Maisem Ali authored
Do not depend on metadata server for auth
-
Erick Fejta authored
-
k8s-merge-robot authored
Automatic merge from submit-queue Allow a FIFO client to requeue under lock The Pop method should allow a caller to requeue an item while under the fifo lock, to avoid races on deletes. @deads2k @wojtek-t
-
k8s-merge-robot authored
Automatic merge from submit-queue Inject service-account.json into test container Add a volume with the service account credentials. This should cause e2e-runner.sh to use them. Fixes #28612
-
k8s-merge-robot authored
Automatic merge from submit-queue kubelete: delete a few bits of dead code Less is more.
-
k8s-merge-robot authored
Automatic merge from submit-queue Remove unnecessary calls to api.GetReference These calls are unnecessary, can be removed. `Eventf` and others just call `GetReference` on the object they are passed. cc @kubernetes/sig-node
-
k8s-merge-robot authored
Automatic merge from submit-queue Removed invalid value []() Id isn't a valid field in a Pod object so kubectl fails with: ``` error validating "glusterfs-pod.json": error validating data: found invalid field id for v1.Pod; if you choose to ignore these errors, turn validation off with --validate=false ```
-
k8s-merge-robot authored
Automatic merge from submit-queue PersistentVolumeClaim.Spec is immutable once created Per https://github.com/kubernetes/kubernetes/pull/28636, PVCs are immutable post-creation in order to enforce quota, limitRange, etc. without being able to game the system. @derekwaynecarr @abhgupta @smarterclayton @kubernetes/sig-storage []()
-
k8s-merge-robot authored
Automatic merge from submit-queue Remove no needed todo ref #19645 #13418 Remove comment about refactoring pod cleanup since we have agree to keep it. cc @yujuhong
-
Erick Fejta authored
-
markturansky authored
-
k8s-merge-robot authored
Automatic merge from submit-queue Optimize priorities in scheduler Ref #28590 It's probably easier to review it commit by commit, since those changes are kind of independent from each other. @davidopp - FYI
-
Adrian Ursu authored
id isn't a valid field in a Pod object so kubectl fails with: error validating "glusterfs-pod.json": error validating data: found invalid field id for v1.Pod; if you choose to ignore these errors, turn validation off with --validate=false
-
Wojciech Tyczynski authored
-
Wojciech Tyczynski authored
-
Wojciech Tyczynski authored
-
Wojciech Tyczynski authored
-
Wojciech Tyczynski authored
-