- 11 Nov, 2016 22 commits
-
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Switch pod eviction client from v1alpha1 to v1beta Generated client 1.5 has a function to evict a pod. The function uses v1alpha1.Eviction object instead of v1beta1. This pr changes the api version that is being used. cc: @davidopp @caesarxuchao
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Set version and job-version in started.json/metadata.json Ref https://github.com/kubernetes/test-infra/issues/1032 We can delete version once all CI jobs are migrated to bootstrap
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue fix issue in reconstruct volume data when kubelet restarts During state reconstruction when kubelet restarts, outerVolueSpecName cannot be recovered by scanning the disk directories. But this information is used by volume manager to check whether pod's volume is mounted or not. There are two possible cases: 1. pod is not deleted during kubelet restarts so that desired state should have the information. reconciler.updateState() will use this inforamtion to update. 2. pod is deleted during this period, reconciler has to use InnerVolumeSpecName, but it should be ok since this information will not be used for volume cleanup (umount)
-
Marcin authored
-
Marcin authored
-
Marcin authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue More unittests for HPA.
-
Erick Fejta authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Federation test util fix - 1 * Make nil and empty map equivalent when testing ObjectMeta equivalence * Add a function that waits for a particular content inside federated store cc: @nikhiljindal @madhusudancs
-
Marcin Wielgus authored
-
Marcin Wielgus authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Improve quota performance for pvc by using shared informer This avoids a list call for each namespace in the resource quota controller when syncing quota.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Do not emit event for AlreadyExists errors Fixes https://github.com/kubernetes/kubernetes/issues/36598 also reduced the clutter of events since the AlreadyExists error is a common error (may be a slow rs cache or a fast resync of the deployment that causes it apart from hash collisions) @kubernetes/deployment
-
Michail Kargakis authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Ensure health check exists before creating target pool We already couple health check deletion with target pool deletion in deleteTargetPools, do the inverse in createTargetPools. See https://github.com/kubernetes/kubernetes/issues/35282#issuecomment-259317589 for why this is necessary. Fixes https://github.com/kubernetes/kubernetes/issues/35282, but the test won't go green till I relieve quota on the project.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Node Conformance & E2E: Get node name from node object. This PR changes the node e2e test framework to get node name from apiserver instead of test flags. When a user tried out the node conformance test, he found that node conformance test will not work properly if kubelet is started with `hostname-override`. The reason is that node conformance test is using [the default node name - `os.Hostname`](https://github.com/kubernetes/kubernetes/blob/master/test/e2e_node/e2e_node_suite_test.go#L124), which may be different from `hostname-override`. This will cause test pods not scheduled, and eventually test timeout. We can expose a flag from node conformance test, and let user set node name themselves if they are using `hostname-override` on kubelet. However, let the framework automatically detect it from apiserver is more user friendly. /cc @kubernetes/sig-node This PR 1) only changes node e2e test framework; 2) fixes a problem in node conformance test which is a 1.5 feature. @saad-ali Can we have this in 1.5?
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue README: stop linking to a 18 month old version We are proud of the v1.0 release but lets give users context on the date it was released and not drive them to the actual release since they should be using the latest release instead.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Expand documentation and TODOs in a few packages I was reading through unfamiliar code and mostly added TODOs and expanded and clarified documentations. There are a couple of things that are real code changes: - Removed some unused constants - Changed `workqueue.Parallize` to clamp the number of worker goroutines to the number of items to be processed. - Added another unit test to `workqueue.queue`. I thought I found a bug (I was wrong) and wrote a unit test to isolate. I figure the extra test is worth keeping.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue CRI: general grammar/spelling/consistency cleanup No semantic changes, but a lot of shuffling of docstrings to make things more consistent. In particular, standardise on the zeroth-article (i.e. prefer `// Version` to `// The version`) and ending all docstrings with periods. (This knowingly conflicts with #36446 and intentionally omits changing the Annotations field - I'll rebase this or that respectively as necessary.)
-
bprashanth authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Ensure proper serialization of updates and creates in federation test watcher Fix for finalizer test problems. The issue there was that the updates were coming out of order. It was caused by firing updates in new goroutines in test watcher. The proper solution is to order them in a queue and fire in order on a single goroutine. Ref: https://github.com/kubernetes/kubernetes/issues/36473#issuecomment-259605870 cc: @nikhiljindal @madhusudancs
-
Jing Xu authored
During state reconstruction when kubelet restarts, outerVolueSpecName cannot be recovered by scanning the disk directories. But this information is used by volume manager to check whether pod's volume is mounted or not. There are two possible cases: 1. pod is not deleted during kubelet restarts so that desired state should have the information. reconciler.updateState() will use this inforamtion to update. 2. pod is deleted during this period, reconciler has to use InnerVolumeSpecName, but it should be ok since this information will not be used for volume cleanup (umount)
-
- 10 Nov, 2016 18 commits
-
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix wrong comparison var in e2e_node density test
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add support for SourceIP preservation in Azure LBs @thockin @colemickens now that we are setting DSR for Azure LBs this should "just work"
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix getting cgroup pids Fixes https://github.com/kubernetes/kubernetes/issues/35214, https://github.com/kubernetes/kubernetes/issues/33232 Verified manually, but I didn't have time to run all the e2e's yet (will check it in the morning). This should be cherry-picked into 1.4, and merged into 1.5 (/cc @saad-ali ) ```release-note Fix fetching pids running in a cgroup, which caused problems with OOM score adjustments & setting the /system cgroup ("misc" in the summary API). ``` /cc @kubernetes/sig-node
-
Random-Liu authored
-
Marcin Wielgus authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Wait for deployment in the storage in federated deployment controller test cc: @nikhiljindal
-
Tim St. Clair authored
-
Tim St. Clair authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue bump golang to 1.7.3 <!-- 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**: bumps the go version to 1.7.3 **Which issue this PR fixes** _(optional, in `fixes #<issue number>(, #<issue_number>, ...)` format, will close that issue when PR gets merged)_: fixes # **Special notes for your reviewer**: **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`. -->
-
Marcin authored
-
Marcin Wielgus authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Update https-nginx example Update how to edit the configmap. Since we are not going to support `kubeectl replace configmap cmName --from-file=filename` in `v1.5`. And update the `inotifywait` command. Fixes: #36489
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add dnsmasq-metrics to the standard DNS pod
-
Michael Taufen authored
-
Brendan Burns authored
-
Brandon Philips authored
We are proud of the v1.0 release but lets give users context on the date it was released and necessarily drive them to the actual release since they should be using the latest release instead.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Do not handle AlreadyExists errors yet Until we fix https://github.com/kubernetes/kubernetes/issues/29735 (use a new hashing algo) we should not handle AlreadyExists (was added recently in the perma-failed PR). @kubernetes/deployment
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Update staging client-go Executed commands: ``` git fetch --all git merge upstream/master godep restore ./hack/update-staging-client-go.sh ``` cc: @caesarxuchao @lavalamp
-