Commit Graph

39271 Commits

Author SHA1 Message Date
Jeff Lowdermilk
3766787458 Document config options for gcp auth provider plugin. 2016-11-21 10:56:39 -08:00
Kubernetes Submit Queue
0664405954 Merge pull request #37021 from Crassirostris/fluentd-image-version-bump
Automatic merge from submit-queue

Bump fluentd-gcp image version

To propagate https://github.com/kubernetes/kubernetes/pull/36993

Including release noted for the whole bunch of fluentd changes (https://github.com/kubernetes/kubernetes/pull/35618 mainly):

```release-note
Default logging subsystem's resiliency was greatly improved, fluentd memory consumption and OOM error probability was reduced.
```

@piosz
2016-11-17 13:52:02 -08:00
Mik Vyatskov
aa31f7bc02 Bump fluentd-gcp image version 2016-11-17 21:21:10 +01:00
Kubernetes Submit Queue
70296869e9 Merge pull request #36919 from Random-Liu/remove-dependency-on-flags
Automatic merge from submit-queue

Node E2E: Remove kubelet related flags

This PR:
1. **Add `KubeletConfig` in test context.** The configuration is dynamically retrieved from kubelet `configz/` endpoint after test node registers itself.
2. **Change tests to look at `KubeletConfig` instead of other kubelet related fields in test context.**
3. **Remove kubelet related flags from node e2e.** Add `kubelet-flags` to pass kubelet flags all together.

Why do we need this change?
1. This is required by **node soaking test and node conformance test**.
  * **For node soaking test.** We'll have one job start the test environment, and another job running the actual test again and again. It's hard to tell the test by flag how kubelet is configured.
  * **For node conformance test.** Kubelet is usually started by user. It's hard and troublesome to tell the test by flag how kubelet is configured.
2. **No need to add another flag in node e2e for each kubelet flag we want to set in the test.** Just directly add the kubelet flag into `kubelet-flags`.

In the future,
1. Kubelet start logic should be moved outside of the test. We should have standard kubelet launcher or standard cloud-init node setup script etc.
2. The test should validate kubelet configuration:
  * Whether the configuration is production ready?
  * Whether the configuration has conflicts?
  * Whether some configuration conflict with node e2e/conformance test is turned on (cloud provider etc.)? (Some configurations need to be turned off when running node e2e/conformance test)
  * ...

/cc @kubernetes/sig-node
2016-11-17 11:32:57 -08:00
Kubernetes Submit Queue
1cc5b61aed Merge pull request #36993 from Crassirostris/docker-logs-time-format
Automatic merge from submit-queue

Remove fixed docker daemon log time format in fluentd configs

Fix https://github.com/kubernetes/kubernetes/issues/36893

Also, probably will fix https://github.com/kubernetes/kubernetes/issues/36890

@piosz
2016-11-17 10:26:59 -08:00
Random-Liu
87a9d94f24 Update bazel. 2016-11-17 10:18:00 -08:00
Random-Liu
edf7608c51 Remove kubelet related flags from node e2e. Add a single flag kubelet-flags to pass kubelet flags all together. 2016-11-17 10:17:32 -08:00
Random-Liu
090809d8ad Remove dependency on kubelet related flags. 2016-11-17 10:17:32 -08:00
Kubernetes Submit Queue
08204bea62 Merge pull request #36849 from janetkuo/e2e-statefulset-update
Automatic merge from submit-queue

Add e2e test for statefulset updates

Verify that one can (manually) update statefulset template 

cc @erictune @foxish @kow3ns @kubernetes/sig-apps
2016-11-17 10:12:21 -08:00
Kubernetes Submit Queue
5efdea63b2 Merge pull request #37001 from gmarek/routes
Automatic merge from submit-queue

Wait for all Nodes to be schedulable before running e2e tests

This should fix the problem we're seeing when running tests on large clusters.

cc @dchen1107
2016-11-17 09:03:30 -08:00
Kubernetes Submit Queue
3ed6000c82 Merge pull request #36994 from gmarek/taints
Automatic merge from submit-queue

Delete taint annotation when removing last taint

It messes with debugging of tests failures.

cc @davidopp @kevin-wangzefeng
2016-11-17 08:26:31 -08:00
gmarek
35626b2a7b Wait for all Nodes to be schedulable before running e2e tests 2016-11-17 16:43:35 +01:00
gmarek
eecc840074 Delete taint annotation when removing last taint 2016-11-17 16:02:34 +01:00
Mik Vyatskov
cf845eda7c Remove fixed docker daemon log time format in fluentd configs 2016-11-17 15:52:07 +01:00
Kubernetes Submit Queue
e120433b54 Merge pull request #36986 from gmarek/secrets
Automatic merge from submit-queue

Allow passing custom list of admission plugins to kubemark

Ref. #36985
2016-11-17 04:21:33 -08:00
Kubernetes Submit Queue
f7f1533a3b Merge pull request #35697 from shashidharatd/upgrade-tests
Automatic merge from submit-queue

Add more test cases to k8s e2e upgrade tests

**Special notes for your reviewer**: 
Added guestbook, secrets, daemonsets, configmaps, jobs to e2e upgrade tests according to the discussions in #35078
Still need to run these test cases in real setup, raised a PR here for initial comments

@quinton-hoole
2016-11-17 04:07:26 -08:00
gmarek
08d60999fc Allow passing custom list of admission plugins to kubemark 2016-11-17 12:32:41 +01:00
Kubernetes Submit Queue
4241a42ad5 Merge pull request #36965 from Random-Liu/fix-truncate-hostname
Automatic merge from submit-queue

Fix hostname truncate.

Fixes https://github.com/kubernetes/kubernetes/issues/36951.

This PR will keep truncating the hostname until the ending character is valid.

/cc @kubernetes/sig-node 

Mark v1.5 because this is a bug fix.
/cc @saad-ali
2016-11-17 02:03:31 -08:00
Kubernetes Submit Queue
424286996a Merge pull request #36764 from ymqytw/make_edit_before_create_iterate
Automatic merge from submit-queue

make kubectl create --edit iterate

`kubectl create --edit` is broken after #36148 merged.
`kubectl create --edit` will fail when a manifest that contains multiple resources.
I guess the root cause is that dynamic typer doesn't support a list of resources currently.

This PR makes `kubectl create --edit` iterate again as `kubectl create`.
2016-11-17 01:25:34 -08:00
Kubernetes Submit Queue
47a431e82f Merge pull request #36336 from justinsb/federation_dns_hosted_zone_2
Automatic merge from submit-queue

Federation: allow specification of dns zone by ID
2016-11-17 00:49:09 -08:00
Kubernetes Submit Queue
68539c02c1 Merge pull request #36924 from krousey/e2eutil
Automatic merge from submit-queue

Replace controller presence checking logic

fixes #36912
2016-11-17 00:11:11 -08:00
Kubernetes Submit Queue
5f86fef169 Merge pull request #36973 from kubernetes/revert-33850-add_e2e_test_for_kubectl_in_pod
Automatic merge from submit-queue

Revert "add e2e test for kubectl in a Pod"

Reverts kubernetes/kubernetes#33850

That PR introduced a test `Kubectl should be able to talk to api server kubectl running in a pod could talk to api server` that runs against GKE.

Ever since the PR merged the test has been failing against [kubernetes-e2e-gke](https://k8s-gubernator.appspot.com/builds/kubernetes-jenkins/logs/kubernetes-e2e-gke) though it was initially passing in [kubernetes-e2e-gci-gke](https://k8s-gubernator.appspot.com/builds/kubernetes-jenkins/logs/kubernetes-e2e-gci-gke). Presumably this was because the path to kubectl was different between GCI and container-vm (the two test suites).

PR https://github.com/kubernetes/kubernetes/pull/36864 attempted to fix this, but ended up breaking the test in both suites. That PR has been reverted (https://github.com/kubernetes/kubernetes/pull/36971).

Because the test introduced in kubernetes/kubernetes#33850 is still broken, it is being reverted (we should've reverted immediately after it merged instead of waiting this long).
2016-11-16 23:33:46 -08:00
Kubernetes Submit Queue
4dd17995fa Merge pull request #36918 from bprashanth/proxy_retry
Automatic merge from submit-queue

Add clarity/retries to proxy url test

Improve one segment of the kube-proxy networking test by:      
1. Retrying for 30s 
2. Bucketing into 2 failure modes
3. Adding some clarity by describing the exec pod on failure

Althought 1 shouldn't be necessary, I don't think we lose anything if the kube-proxy convenience endpoint doesn't respond immediately, and if it fails for 30s straight it is indicative of something that requires attention probably within 1.5. 

Fixes https://github.com/kubernetes/kubernetes/issues/32436
2016-11-16 22:54:50 -08:00
Kubernetes Submit Queue
a988f71ef0 Merge pull request #36949 from fejta/upload
Automatic merge from submit-queue

Require BOOTSTRAP_MIGRATION, JENKINS_BUILD_STARTED or JENKINS_BUILD_F…

If we do not do this then we upload finished.json and update latest-build.txt before the build fiinshes, breaking the SQ
2016-11-16 22:20:55 -08:00
Saad Ali
172e7562fb Revert "add e2e test for kubectl in a Pod" 2016-11-16 21:38:19 -08:00
Saad Ali
db72f92cb3 Merge pull request #36971 from kubernetes/revert-36864-fix-path-to-kubectl-in-gke-test
Revert "Fix path to kubectl on host in kubectl-in-pod"
2016-11-16 21:37:46 -08:00
Saad Ali
2aa2cf3800 Revert "Fix path to kubectl on host in kubectl-in-pod" 2016-11-16 20:44:25 -08:00
Random-Liu
e9f1b0f972 Fix hostname truncate. 2016-11-16 18:09:31 -08:00
Saad Ali
01897bb3c0 Merge pull request #36864 from dims/fix-path-to-kubectl-in-gke-test
Fix path to kubectl on host in kubectl-in-pod
2016-11-16 17:21:13 -08:00
Erick Fejta
32e2f22019 Require BOOTSTRAP_MIGRATION, JENKINS_BUILD_STARTED or JENKINS_BUILD_FINISHED 2016-11-16 17:20:04 -08:00
Kris
5a87385342 Replace controller presence checking logic 2016-11-16 16:12:26 -08:00
Kubernetes Submit Queue
43110dd64d Merge pull request #36920 from yujuhong/bump_image_version
Automatic merge from submit-queue

Bump gci image version for cri builds

#36681 didn't change all the configs.
2016-11-16 15:46:00 -08:00
Kubernetes Submit Queue
add6ed4dd1 Merge pull request #36719 from saturnism/patch-3
Automatic merge from submit-queue

Fixed typo - cluser -> cluster, and replicasets -> ReplicaSet for consistency

<!--  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**:

**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`. 
-->
```release-note
```
2016-11-16 15:09:03 -08:00
bprashanth
29a5cb7a9c Add clarity/retries to proxy url test 2016-11-16 14:45:35 -08:00
Kubernetes Submit Queue
92b40dc2f5 Merge pull request #36848 from jingxu97/Nov/gluster
Automatic merge from submit-queue

Enable NFSv4 and GlusterFS tests on cluster e2e tests

Enable NFSv4 and GlusterFS tests on cluster e2e tests for GCI images
only.
2016-11-16 14:19:24 -08:00
Yu-Ju Hong
6ba2c7b857 Bump gci image version for cri builds 2016-11-16 14:09:51 -08:00
Kubernetes Submit Queue
97945b3fa5 Merge pull request #36884 from feiskyer/fix-cgroup-root
Automatic merge from submit-queue

Fix syntax error in local-up-cluster.sh when CGROUP_ROOT is set

Fix syntax error when `CGROUP_ROOT` is set, or it will complain a following error:

```
hack/local-up-cluster.sh: line 39: CGROUP_ROOT: "": syntax error: operand expected (error token is """")
```

cc/ @derekwaynecarr
2016-11-16 13:42:22 -08:00
Kubernetes Submit Queue
3d64d919e4 Merge pull request #36833 from mandarjog/issue_36652
Automatic merge from submit-queue

Handle Empty clusterCIDR

**What this PR does / why we need it**:
Handles empty clusterCIDR by skipping the corresponding rule.

**Which issue this PR fixes** 
fixes #36652

**Special notes for your reviewer**:
1. Added test to check for presence/absence of XLB to SVC rule
2. Changed an error statement to log rules along with the error string in case of a failure; This ensures that full debug info is available in case of iptables-restore errors.


Empty clusterCIDR causes invalid rules generation.
Fixes issue #36652
2016-11-16 13:42:11 -08:00
Kubernetes Submit Queue
f918dd64c4 Merge pull request #36901 from leitzler/issue_36858_SA2003
Automatic merge from submit-queue

Fix SA2003, deferred Lock right after locking

<!--  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**:
Fixes a re-locking right after a lock. This is a part if issue #36858.

**Special notes for your reviewer**:
N/A

**Release note**:
NONE
2016-11-16 13:04:09 -08:00
Kubernetes Submit Queue
1085ce6081 Merge pull request #36768 from yujuhong/recover_from_failure
Automatic merge from submit-queue

dockershim: remove sandbox container upon naming conflicts

We have observed that, after failing to create a container due to "device or
resource busy", docker may end up having inconsistent internal state. One
symptom is that docker will not report the existence of the "failed to create"
container, but if kubelet tries to create a new container with the same name,
docker will error out with a naming conflict message.

To work around this, this commit parses the creation error message and if there
is a naming conflict, it would attempt to remove the existing container.
2016-11-16 12:27:36 -08:00
Kubernetes Submit Queue
922dff3e39 Merge pull request #36820 from kevin-wangzefeng/fix-kubectl-taint-flake
Automatic merge from submit-queue

fix kubectl taint test flake

<!--  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**:
Kubectl taint tests fail often recently, this PR is trying to fix it.

**Which issue this PR fixes**: ref #29503, #32535

**Special notes for your reviewer**:
This PR cannot 100% fix the flake, but just reduce the failing rate, if the two "kubectl taint" tests are running at the same time, it still has chance to fail.
Maybe should mark the tests "Serial" (see also #31906, #36781), but then they won't run for each PR.
2016-11-16 11:48:07 -08:00
Yu-Ju Hong
5c90908eb0 dockershim: remove container upon naming conflicts
We have observed that, after failing to create a container due to "device or
resource busy", docker may end up having inconsistent internal state. One
symptom is that docker will not report the existence of the "failed to create"
container, but if kubelet tries to create a new container with the same name,
docker will error out with a naming conflict message.

To work around this, this commit parses the creation error message and if there
is a naming conflict, it would attempt to remove the existing container.
2016-11-16 10:20:16 -08:00
Kubernetes Submit Queue
0f95b262dc Merge pull request #35460 from humblec/gluster-gid-prov-2
Automatic merge from submit-queue

Use Gid when provisioning Gluster Volumes.

Bug # https://github.com/openshift/origin/issues/11556
2016-11-16 10:15:03 -08:00
Jing Xu
afbf5f52e5 Update volumes.go 2016-11-16 10:04:12 -08:00
Wojciech Tyczynski
9fc4dbcacd Merge pull request #36899 from gmarek/constraints
Update API server CPU constraints in the density test
2016-11-16 17:02:15 +01:00
gmarek
0f9c0678b7 Update API server CPU constraints in the density test 2016-11-16 16:33:53 +01:00
Jing Xu
64955959e6 Enable NFSv4 and GlusterFS tests on cluster e2e tests
Enable NFSv4 and GlusterFS tests on cluster e2e tests for GCI images
only.
2016-11-16 07:27:26 -08:00
Humble Chirammal
7a0d219d12 Use Gid when provisioning Gluster Volumes.
BUG # https://github.com/openshift/origin/issues/11556

Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
2016-11-16 19:43:51 +05:30
Kubernetes Submit Queue
28d273c8b2 Merge pull request #36810 from gmarek/secrets
Automatic merge from submit-queue

Add ServiceAccounts to kubemark

cc @yujuhong
2016-11-16 06:01:30 -08:00
Kubernetes Submit Queue
193622b31f Merge pull request #36728 from feiskyer/sysctls-docs
Automatic merge from submit-queue

CRI: add docs for sysctls

#34830 adds `sysctls` features in CRI, it is based on sandbox annotations, this PR adds docs for it. 

@yujuhong @timstclair @jonboulle
2016-11-16 02:58:42 -08:00