- 23 Nov, 2016 40 commits
-
-
Chao Xu authored
-
Chao Xu authored
-
Chao Xu authored
-
Saad Ali authored
Collect installation and configuration service logs for tests
-
Dawn Chen authored
Fix cross-build for memcg notification
-
Michael Taufen authored
-
Dawn Chen authored
Revert list of primitives fix
-
Dawn Chen authored
Fix a bug in scheduler happening after retrying unsuccessful bindings
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix an else branch in trusty/configure-helper.sh Similar to #37358, for fixing #37257 on trusty.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix an else branch in configure-helper.sh **What this PR does / why we need it**: bug fix for upgrade.sh needed in 1.5 **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #37257
-
Dawn Chen authored
Skip StatefulSet e2e tests if this resource is not found
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add a known issue in the CRI doc Also added some more github issue numbers for them. /cc @Random-Liu @freehan @timstclair
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Use shasum if sha1sum doesn't exist in the path **What this PR does / why we need it**: bug fix for running upgrade.sh from a mac **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #37355
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Removed "feature" tag
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue kubemark: fix start-kubemark.sh
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Node E2E: Fix remote log fetching. For issue https://github.com/kubernetes/kubernetes/issues/37333. This will help debug https://github.com/kubernetes/kubernetes/issues/37333. Mark v1.5 because this helps debug an issue https://github.com/kubernetes/kubernetes/issues/37333, which was originally https://github.com/kubernetes/kubernetes/issues/35935. /cc @saad-ali @yujuhong @dchen1107 @jingxu97 /cc @kubernetes/sig-node
-
Janet Kuo authored
-
Piotr Szczesniak authored
Revert "Remove [Slow] from statefulset basic tests"
-
Yu-Ju Hong authored
-
Derek Carr authored
-
Robert Bailey authored
-
Piotr Szczesniak authored
Revert "Modify GCI mounter to enable NFSv3"
-
Piotr Szczesniak authored
-
Robert Bailey authored
-
Jerzy Szczepkowski authored
Removed "feature" tag so that ha master tests will run by default.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Modify GCI mounter to enable NFSv3 In order to make NFSv3 work, mounter needs to start rpcbind daemon. This change modify mounter's Dockerfile and mounter script to start the rpcbind daemon if it is not running on the host. After this change, need to make push the image and update the sha number in Changelog.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Update [Feature:PetSet] e2e tests to [Feature:StatefulSet] <!-- Thanks for sending a pull request! Here are some tips for you: 1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md 2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md 3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes --> **What this PR does / why we need it**: Update StatefulSet e2e test feature tags from [Feature:PetSet] to [Feature:StatefulSet] **Special notes for your reviewer**: Ref test-infra changes https://github.com/kubernetes/test-infra/pull/1151 cc @erictune @foxish @kow3ns @enisoc @kubernetes/sig-apps **Release note**: <!-- Steps to write your release note: 1. Use the release-note-* labels to set the release note state (if you have access) 2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. --> ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue populate ready replicas and aviable replicas to federated replicaset … populate ready replicas and aviable replicas to federated replicaset status @nikhiljindal #33312 #29481 #32771 @deepak-vij
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Guard the ready replica checking by server version I fixed replica readiness checking for 1.4->1.5 upgrades by using a field that only exists in versions >=1.4.0 in #36924 This fixed a lot of issues in 1.4->1.5 upgrade testing, but did not fix 1.3->1.5 upgrade tests. I've disabled replica checking for 1.3 masters as the old logic was broken anyway. This will not affect the 1.3 CI tests. Just 1.3 -> {1.4, 1.5} upgrade tests. https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke-container_vm-1.3-container_vm-1.5-upgrade-cluster-new/330?log is an example of this breakage. This is the tell-tale logs: ```console Nov 22 09:40:50.469: INFO: 11 / 11 pods in namespace 'kube-system' are running and ready (506 seconds elapsed) Nov 22 09:40:50.469: INFO: expected 5 pod replicas in namespace 'kube-system', 0 are Running and Ready. Nov 22 09:40:50.469: INFO: POD NODE PHASE GRACE CONDITIONS ``` -
Kubernetes Submit Queue authored
Automatic merge from submit-queue kubelet: eviction: add memcg threshold notifier to improve eviction responsiveness This PR adds the ability for the eviction code to get immediate notification from the kernel when the available memory in the root cgroup falls below a user defined threshold, controlled by setting the `memory.available` siginal with the `--eviction-hard` flag. This PR by itself, doesn't change anything as the frequency at which new stats can be obtained is currently controlled by the cadvisor housekeeping interval. That being the case, the call to `synchronize()` by the notification loop will very likely get stale stats and not act any more quickly than it does now. However, whenever cadvisor does get on-demand stat gathering ability, this will improve eviction responsiveness by getting async notification of the root cgroup memory state rather than relying on polling cadvisor. @vishh @derekwaynecarr @kubernetes/rh-cluster-infra
-
Random-Liu authored
-
Hongchao Deng authored
-
Yu-Ju Hong authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue retry some operation in the gke kube-up.sh ref https://github.com/kubernetes/kubernetes/issues/36895#issuecomment-262080246
-