- 02 Jun, 2016 40 commits
-
-
Tim Hockin authored
-
Tim Hockin authored
Add it as a special case package root and import the license file. This was the only UNKNOWN license, prior to the change to not look at upstream repo state.
-
k8s-merge-robot authored
Automatic merge from submit-queue rkt: Get logs via syslog identifier This change works around https://github.com/coreos/rkt/issues/2630 Without this change, logs cannot reliably be collected for containers with short lifetimes. With this change, logs cannot be collected on rkt versions v1.6.0 and before. I'd like to also bump the required rkt version, but I don't want to do that until there's a released version that can be pointed to (so the next rkt release). I haven't added tests (which were missing) because this code will be removed if/when logs are retrieved via the API. I have run E2E tests with this merged in and verified the tests which previously failed no longer fail. cc @yifan-gu
-
David McMahon authored
-
k8s-merge-robot authored
Automatic merge from submit-queue Enable node e2e accounting on systemd Updated the e2e setup.sh script to enable cpu and memory accounting. Related to https://github.com/kubernetes/kubernetes/issues/26198 /cc @pwittrock
-
k8s-merge-robot authored
Automatic merge from submit-queue read gluster log to surface glusterfs plugin errors properly in describe events glusterfs.go does not properly expose errors as all mount errors go to a log file, I propose we read the log file to expose the errors without asking the users to 'go look at this log' This PR does the following: 1. adds a gluster option for log-level=ERROR to remove all noise from log file 2. change log file name and path based on PV + Pod name - so specific per PV and Pod 3. create a utility to read the last two lines of the log file when failure occurs old behavior: ``` 13s 13s 1 {kubelet 127.0.0.1} Warning FailedMount Unable to mount volumes for pod "bb-gluster-pod2_default(34b18c6b-070d-11e6-8e95-52540092b5fb)": glusterfs: mount failed: Mount failed: exit status 1 Mounting arguments: 192.168.234.147:myVol2 /var/lib/kubelet/pods/34b18c6b-070d-11e6-8e95-52540092b5fb/volumes/kubernetes.io~glusterfs/pv-gluster glusterfs [log-file=/var/lib/kubelet/plugins/kubernetes.io/glusterfs/pv-gluster/glusterfs.log] Output: Mount failed. Please check the log file for more details. ``` improved behavior: (updated after suggestions from community) ``` 34m 34m 1 {kubelet 127.0.0.1} Warning FailedMount Unable to mount volumes for pod "bb-multi-pod1_default(e7d7f790-0d4b-11e6-a275-52540092b5fb)": glusterfs: mount failed: Mount failed: exit status 1 Mounting arguments: 192.168.123.222:myVol2 /var/lib/kubelet/pods/e7d7f790-0d4b-11e6-a275-52540092b5fb/volumes/kubernetes.io~glusterfs/pv-gluster2 glusterfs [log-level=ERROR log-file=/var/lib/kubelet/plugins/kubernetes.io/glusterfs/pv-gluster2/bb-multi-pod1-glusterfs.log] Output: Mount failed. Please check the log file for more details. the following error information was pulled from the log to help resolve this issue: [2016-04-28 14:21:29.109697] E [socket.c:2332:socket_connect_finish] 0-glusterfs: connection to 192.168.123.222:24007 failed (Connection timed out) [2016-04-28 14:21:29.109767] E [glusterfsd-mgmt.c:1819:mgmt_rpc_notify] 0-glusterfsd-mgmt: failed to connect with remote-host: 192.168.123.222 (Transport endpoint is not connected) ``` also this PR is alternate approach to : #24624 -
k8s-merge-robot authored
Automatic merge from submit-queue Add retries for make in start-kubemark Fix. #25872
-
k8s-merge-robot authored
Automatic merge from submit-queue e2e: fix node restart tests The test does not run in the per-PR suite, so e2e is not required.
-
k8s-merge-robot authored
Automatic merge from submit-queue List RSes once when getting old/new RSes in deployment e2e tests Ref #26509 []()
-
k8s-merge-robot authored
Automatic merge from submit-queue fix kubectl patch example Based on https://github.com/kubernetes/kubernetes/pull/25746, fix the kubectl example. cc @tobstarr
-
k8s-merge-robot authored
Automatic merge from submit-queue rkt: Add pod selinux support. Currently only pod level selinux context is supported, besides when running selinux, we will not be able to use the overlay fs, see: https://github.com/coreos/rkt/issues/1727#issuecomment-173203129. cc @kubernetes/sig-node @alban @mjg59 @pmorie
-
Yu-Ju Hong authored
Allow pods to be succeeded or running.
-
k8s-merge-robot authored
Automatic merge from submit-queue adding a few owners for node e2e framework cc @pwittrock This should help spread node e2e PRs.
-
k8s-merge-robot authored
Automatic merge from submit-queue Added logging to file for cluster autoscaler
-
Scott Creeley authored
-
k8s-merge-robot authored
Automatic merge from submit-queue federation: Update the list of supported admission controls Ref https://github.com/kubernetes/kubernetes/pull/26298#issuecomment-221697124 In 1.3, we are going to support only AlwaysAdmit and AlwaysDeny admission controls. Updating the documentation accordingly. @kubernetes/sig-cluster-federation
-
Wojciech Tyczynski authored
add logging for flake #26689
-
Wojciech Tyczynski authored
Fix MaxPods test to work with image puller
-
k8s-merge-robot authored
Automatic merge from submit-queue Disable PodAffinity SchedulerPredicates test This feature is disabled, so it's not surprising that tests don't work. cc @davidopp @kevin-wangzefeng @david-mcmahon - this disables the second test that causes failures in SchedulerPredicates suite. When this and #26695 are merged it should be passing in serial.
-
k8s-merge-robot authored
Automatic merge from submit-queue Revert revert of adding resource constraints for master components in density tests The problem was the time when resource constraints were generated. It turns out that the provider is not set there. This version should work. cc @roberthbailey @alex-mohr
-
Piotr Szczesniak authored
-
deads2k authored
-
k8s-merge-robot authored
Automatic merge from submit-queue Fix data race in volume controller unit test. Reactor must be locked when fiddling with reactor.volumes and reactor.claims. Therefore add new functions to add/delete volume/claim with sending an event. Fixes #26345
-
k8s-merge-robot authored
Automatic merge from submit-queue Wait for all nodes to be schedulable in scalability tests
-
gmarek authored
-
gmarek authored
-
k8s-merge-robot authored
Automatic merge from submit-queue federation: Adding federation controller manager to federation e2es Adding federation controller manager to federation e2es. Havent been able to verify that this works: https://github.com/kubernetes/kubernetes/pull/25125#issuecomment-222860475 Followed the same patter as federation-apiserver and made the changes at same places, so hopefully should work :)
-
k8s-merge-robot authored
Automatic merge from submit-queue Fixed problem with too long name in e2e autoscaling tests. []() Fixed problem with too long name in e2e autoscaling tests.
-
k8s-merge-robot authored
Automatic merge from submit-queue Rebuild elasticsearch image to include changes since 1.2 Fixes #25360. I've pushed the image to GCR. @jimmidyson @keontang @vishh
-
Wojciech Tyczynski authored
-
k8s-merge-robot authored
Automatic merge from submit-queue Fix sed transformation for new kube-dns yaml <!-- 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. --> ```release-note * Use the release-note-* labels to set the release note state * Clear this block to use the PR title as the release note -OR- * Enter your extended release note here ``` []()
-
Jerzy Szczepkowski authored
Fixed problem with too long name in e2e autoscaling tests.
-
k8s-merge-robot authored
Automatic merge from submit-queue Move the defaults setting of GCI to util.sh fixes #26291 This change recovers some of the side effects of https://github.com/kubernetes/kubernetes/pull/26197, i.e., keeps the defaults of `NODE_IMAGE` and `NODE_IMAGE_PROJECT` to `MASTER_IMAGE` and `MASTER_IMAGE_PROJECT`, for backward compatibility. Although it keeps `OS_DISTRIBUTION` defaulting to `gci`, the default settings of these vars are moved to `cluster/gce/util.sh` and conditioned on `OS_DISTRIBUTION==gci`. @euank @roberthbailey Can you review?
-
nikhiljindal authored
-
k8s-merge-robot authored
Automatic merge from submit-queue Add direct serializer Fix #25589. Implemented a direct codec that doesn't do conversion, but sets the group, version and kind before serialization as Clayton suggested [here](https://github.com/kubernetes/kubernetes/issues/25589#issuecomment-219168009). First commit is cherry-picked from #24826. @kubernetes/sig-api-machinery
-
k8s-merge-robot authored
Automatic merge from submit-queue Suppress non error logs from ssh commands in node e2e framework. Fixes #25713
-
k8s-merge-robot authored
Automatic merge from submit-queue Adding logs in deployment for debugging Ref #26509 []()
-
k8s-merge-robot authored
Automatic merge from submit-queue Integrate federated service DNS record management Integrate federated service DNS record management.
-
nikhiljindal authored
-
k8s-merge-robot authored
Automatic merge from submit-queue GKE provider: Tear down firewall rules last []() It turns out, it's faster to do it in this order for large clusters. Along the way: Do it in parallel
-