- 30 Jul, 2016 5 commits
-
-
Random-Liu authored
-
Random-Liu authored
-
Random-Liu authored
-
k8s-merge-robot authored
Automatic merge from submit-queue make log description more readable
-
k8s-merge-robot authored
Automatic merge from submit-queue Fix 29451 Fix #29451. I've also checked other tests in that file to make sure they don't have similar problems. The issue is P0 and will block the submit queue, so I marked this PR as P0.
-
- 29 Jul, 2016 35 commits
-
-
k8s-merge-robot authored
Automatic merge from submit-queue Trigger container cleanup within a pod when a container exiting event is detected #25239
-
k8s-merge-robot authored
Automatic merge from submit-queue Re-org of the openstack cloud provider
-
k8s-merge-robot authored
Automatic merge from submit-queue Combine the const definition The PR combine the const definition in service.go, and it seems more concise, I think.
-
k8s-merge-robot authored
Automatic merge from submit-queue fix a wrong word in the comment
-
k8s-merge-robot authored
Automatic merge from submit-queue Adding label-config yaml file consumed by check-labels munger https://github.com/kubernetes/contrib/issues/1423 Added labels configuration file to help maintain and synchronize labels across repositories.
-
k8s-merge-robot authored
Automatic merge from submit-queue 2nd iteration of Gobindata + RepoRoot removals. Part of my overall life mission to kill reporoot. Fixes part of #24348 cc @kubernetes/sig-testing .
-
k8s-merge-robot authored
Automatic merge from submit-queue pkg/various: plug leaky time.New{Timer,Ticker}s According to the documentation for Go package time, `time.Ticker` and `time.Timer` are uncollectable by garbage collector finalizers. They leak until otherwise stopped. This commit ensures that all remaining instances are stopped upon departure from their relative scopes. Similar efforts were incrementally done in #29439 and #29114. ```release-note * pkg/various: plugged various time.Ticker and time.Timer leaks. ``` -
k8s-merge-robot authored
Automatic merge from submit-queue Keep retry times the same for each place where trying to ensure DNS Records There are three places where ensureDnsRecords is retried. But they have different retry times. One place [(here)](https://github.com/xiangpengzhao/kubernetes/blob/master/federation/pkg/federation-controller/service/endpoint_helper.go#L107) is clientRetryCount but other two [(here](https://github.com/xiangpengzhao/kubernetes/blob/master/federation/pkg/federation-controller/service/endpoint_helper.go#L138) and [here)](https://github.com/xiangpengzhao/kubernetes/blob/master/federation/pkg/federation-controller/service/endpoint_helper.go#L161) are clientRetryCount + 1. Though this case doesn't have any influence, shouldn't we keep retry times the same each place? also fix other nits: use the same log level. log the error in each loop. cc @quinton-hoole
-
Chao Xu authored
-
David McMahon authored
-
k8s-merge-robot authored
Automatic merge from submit-queue dockershim: Implement more functions. Based on #29553. Only the last two commits are new.
-
k8s-merge-robot authored
Automatic merge from submit-queue Update 1.3.3 CHANGELOG with known issues. Just a small update to include known issues with 1.3.3.
-
k8s-merge-robot authored
Automatic merge from submit-queue Add rules for kube-scheduler Just find that we have also missed the rule for `kube-scheduler`. I don't want to mix the rule with #29683 (make help) now. Will merge them finally if #29683 can be merged.
-
k8s-merge-robot authored
Automatic merge from submit-queue Generate federation apiserver extensions replicaset client generate clientset for extensions/ReplicaSet of federation apiserver @nikhiljindal @quinton-hoole, @deepak-vij #24764
-
Jay Vyas authored
bindata and yaml, Gobindata automation bindata utils for generating, go generate match server version gitignore for dirty, ca, rbase, KUBE_ROOT, buildfix (rebased jul-25,29)
-
k8s-merge-robot authored
Automatic merge from submit-queue Update acquire to use newer JitterUntil vs. sleep Fix to prevent https://github.com/kubernetes/kubernetes/issues/26782 which could have had a race on a 0 timer the way it was written before due to changes in wait. I will likely make a PR for some of the recent changes in wait as well.
-
k8s-merge-robot authored
Automatic merge from submit-queue kubelet: use util/iptables, which uses -w (lock wait) where safe cc @thockin @dchen1107
-
xiangpengzhao authored
-
k8s-merge-robot authored
Automatic merge from submit-queue Removed empty line.
-
Timothy St. Clair authored
have caused a race in Until.
-
Rudi Chiarito authored
-
Klaus Ma authored
-
KeZhang authored
-
xiangpengzhao authored
-
k8s-merge-robot authored
Automatic merge from submit-queue Fix race condition found in JitterUntil. This was caused by the recent addition of "sliding" manifested in: https://github.com/kubernetes/kubernetes/issues/26782
-
k8s-merge-robot authored
Automatic merge from submit-queue Add API for StorageClasses This is the API objects only required for dynamic provisioning picked apart from the controller logic. Entire feature is here: https://github.com/kubernetes/kubernetes/pull/29006
-
k8s-merge-robot authored
Automatic merge from submit-queue Remove redundant pod deletion in scheduler predicates tests and fix taints-tolerations e2e ~~In scheduler predicates test, some tests won't clean pods they created when exit with failure, which may lead to pod leak. This PR is to fix it.~~ Remove redundant pod deletion in scheduler predicates tests, since framework.AfterEach() already did the cleanup work after every test. Also fix the test "validates that taints-tolerations is respected if not matching", refer to the change on taint-toleration test in #29003, and https://github.com/kubernetes/kubernetes/pull/24134#discussion_r63794924.
-
foxish authored
-
k8s-merge-robot authored
Automatic merge from submit-queue Initial support for pod eviction based on disk This PR adds the following: 1. node reports disk pressure condition based on configured thresholds 1. scheduler does not place pods on nodes reporting disk pressure 1. kubelet will not admit any pod when it reports disk pressure 1. kubelet ranks pods for eviction when low on disk 1. kubelet evicts greediest pod Follow-on PRs will need to handle: 1. integrate with new image gc PR (https://github.com/kubernetes/kubernetes/pull/27199) 1. container gc policy should always run (will not be launched from eviction, tbd who does that) 1. this means kill pod is fine for all eviction code paths since container gc will remove dead container 1. min reclaim support will just poll summary provider (derek will do follow-on) 1. need to know if imagefs is same device as rootfs from summary (derek follow-on) /cc @vishh @kubernetes/sig-node
-
k8s-merge-robot authored
Automatic merge from submit-queue Check iscsi iface file for transport name When checking for tcp vs hardware transports, check actual iscsi iface file to see if we are using tcp as a transport, rather than relying on just the transport name of 'default'. This fixes the open-iscsi software iscsi initiator for non-default interfaces. fixes #27131
-
k8s-merge-robot authored
Automatic merge from submit-queue Fix kubectl help command PR 48d47b10 broke `kubectl help` command due to wrong check `help for help cmd` . Fixes #29736
-
k8s-merge-robot authored
Automatic merge from submit-queue remove the omitempty tag from CertificateSigningRequestList.Items As a general rule, `Items` should be a required field in all lists. In a followup PR, I'll update the api-convention.md and add a check in the schema registration path to enforce the rule. I need to fix this bug to unblock other work. @kubernetes/api-review-team cc @bgrant0607-cc
-
Yu-Ju Hong authored
-
Yu-Ju Hong authored
-
k8s-merge-robot authored
Automatic merge from submit-queue Add a docker-shim package Add a new docker integration with kubelet using the new runtime API. This change adds the package with the skeleton and implements some of the basic operations. This PR only implements a small sets of functions. The rest of the functions will be implemented in the followup PRs to keep the changes readable, and the reviewers sane. Note: The first commit is from #28396, only the second commit is for review. /cc @kubernetes/sig-node @feiskyer @Random-Liu
-