- 14 Jul, 2017 15 commits
-
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 48082, 48815, 48901, 48824) Add test image name to the OS image field of the perf metrics I'd like to add the resource usage benchmarks for COS m60 (docker 1.13.1) but don't want to remove the existing m59 (docker 1.11.2) [ones](https://github.com/kubernetes/kubernetes/blob/master/test/e2e_node/jenkins/benchmark/benchmark-config.yaml#L51-L71), in order to compare the results between the two docker versions. The `image` reported in the metrics is from `Node.Status.NodeInfo.OSImage`, which is always "Container-Optimized OS from Google" (from `/etc/os-releases`) for COS. So there's no way to differentiate two milestones in the metrics. This PR attaches the [image name](https://github.com/kubernetes/kubernetes/blob/master/test/e2e_node/jenkins/benchmark/benchmark-config.yaml#L52) to the `image` field of the metrics. So it will become "Container-Optimized OS from Google (cos-stable-59-9460-64-0)". See the results of the test run: [performance-memory-containervm-resource1-resource_0.json](https://storage.googleapis.com/ygg-gke-dev-bucket/e2e-node-test/ci-kubernetes-node-kubelet-benchmark/13/artifacts/performance-memory-containervm-resource1-resource_0.json) [performance-memory-coreos-resource1-resource_0.json](https://storage.googleapis.com/ygg-gke-dev-bucket/e2e-node-test/ci-kubernetes-node-kubelet-benchmark/13/artifacts/performance-memory-coreos-resource1-resource_0.json) [performance-memory-gci-resource1-resource_0.json](https://storage.googleapis.com/ygg-gke-dev-bucket/e2e-node-test/ci-kubernetes-node-kubelet-benchmark/13/artifacts/performance-memory-gci-resource1-resource_0.json) **Release note**: ``` None ``` Ref: https://github.com/kubernetes/kubernetes/issues/42926 /sig node /area node-e2e /assign @dchen1107
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 48082, 48815, 48901, 48824) Import kubectl tests in e2e_test.go so they start running. ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 48082, 48815, 48901, 48824) mountpath should be absolute **What this PR does / why we need it**: Should validate the mountpath before mounting to container. Docker forbids mounting to a relative path inside the container. **Which issue this PR fixes** : fixes #48749 **Special notes for your reviewer**: **Release note**: ```release-note MountPath should be absolute ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 48082, 48815, 48901, 48824) Changes for typecasting node in drain **What this PR does / why we need it**: **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #48059 **Special notes for your reviewer**: Precursor to #44944 **Release note**: ```release-note kubectl drain now uses PATCH instead of PUT to update the node. The node object is now of type v1 instead of using internal api. ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Use t.Fatalf instead **What this PR does / why we need it**: we can use t.Fatalf to take place of t.Errorf + t.FailNow() **Release note**: ```release-note NONE ```
-
Chao Xu authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add OWNERS file to kubelet gpu package GPU support is ramping up and we do not have a lot of reviewers that are familiar with the codebase. I added myself as a reviewer and copied a few people from the kubelet OWNERS file as approvers. Signed-off-by:Christopher M. Luciano <cmluciano@us.ibm.com> **Release note**: ``` NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue update release notes for 1.7
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Properly nest code blocks **What this PR does / why we need it**: Markdown code blocks are adjusted to better display on GitHub. See [rendered](https://github.com/gmile/kubernetes/blob/c3fbec766366d98e434acd44e84f2a4fb4f64a6d/cluster/addons/cluster-loadbalancing/glbc/README.md) version. **Release note**: ```release-note Adjust markdown code block in README for Google Load Balancer addon. ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Update docs for user-guide **What this PR does / why we need it**: **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # **Special notes for your reviewer**: **Release note**: ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Updated comments of func in testapi. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #N/A **Special notes for your reviewer**: **Release note**: ```release-note-none ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue [trivial]fix function name in comment **Release note**: ``` NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue add dockershim checkpoint node e2e test Add a bunch of disruptive cases to test kubelet/dockershim's checkpoint work flow. Some steps are quite hacky. Not sure if there is better ways to do things.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 47999, 47890) [Federation] Update namespace support to use the sync controller This PR moves namespaces to use the sync controller. cc: @kubernetes/sig-federation-pr-reviews
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 47999, 47890) LocalPV e2e test with two pods writing/reading to a shared file on one PVC **What this PR does / why we need it**: This PR adds an e2e test where one pod writes to a localPV and another reads from it. This e2e test is for the PersistentLocalVolumes alpha feature. **Which issue this PR fixes**: fixes https://github.com/kubernetes/kubernetes/issues/48832 **Special notes for your reviewer**: You need to setup the PersistentLocalVolumes feature-gate and NODE_LOCAL_SSDS environment variable. For example: ``` KUBE_FEATURE_GATES="PersistentLocalVolumes=true" NODE_LOCAL_SSDS=1 go run hack/e2e.go -- -v --up go run hack/e2e.go -- -v --test --test_args="--ginkgo.focus=\[Feature:LocalPersistentVolumes\]" ``` **Release note**: ```release-note NONE ```
-
- 13 Jul, 2017 16 commits
-
-
Matt Liggett authored
fix gce cloud provider projects api endpoint
-
Phillip Wittrock authored
Also rename the Describe function
-
Minhan Xia authored
-
krousey authored
Revert "Merge pull request #48560 from nicksardo/gce-network-project"
-
Maru Newby authored
-
Ian Chakeres authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 48555, 48849) GCE: Fix panic when service loadbalancer has static IP address Fixes #48848 ```release-note Fix service controller crash loop when Service with GCP LoadBalancer uses static IP (#48848, @nicksardo) ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix subPath existence check to not follow symlink **What this PR does / why we need it**: Volume mounting logic introduced in #43775 and #45623 checks for subPath existence before attempting to create a directory, should subPath not be present. This breaks if subPath is a dangling symlink, os.Stat returns "do not exist" status, yet `os.MkdirAll` can't create directory as symlink is present at the given path. This patch makes existence check to use os.Lstat which works for normal files/directories as well as doesn't not attempt to follow symlink, therefore it's "do not exist" status is more reliable when making a decision whether to create directory or not. subPath symlinks can be dangling in situations where kubelet is running in a container itself with access to docker socket, such as CoreOS's kubelet-wrapper script **Release note**: ```release-note Fix pods failing to start when subPath is a dangling symlink from kubelet point of view, which can happen if it is running inside a container ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue add [sig-apps] identifier to relevant upgrade tests **What this PR does / why we need it**: This PR adds [sig-apps] identifier to relevant upgrade tests. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: xref #48839 **Special notes for your reviewer**: **Release note**: ```release-note ```
-
Nick Sardo authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue add [sig-apps] prefix to workload e2e tests **What this PR does / why we need it**: This PR adds [sig-apps] prefix to workload e2e tests in accord to requirements of adding a SIG dashboard to testgrid. Refer PR #48781 for guidelines. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # **Special notes for your reviewer**: **Release note**: ```release-note ```
-
Chao Xu authored
-
ravisantoshgudimetla authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Support GCE alpha/beta api endpoint override fixes: https://github.com/kubernetes/kubernetes/issues/48568
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue maxinflight handler should let panicrecovery handler call NewLogged Fixes #48700 #48782 /cc @deads2k @sttts
-
- 12 Jul, 2017 9 commits
-
-
Jun Xiang Tee authored
-
Jun Xiang Tee authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 46738, 48827, 48831) Add test for kubectl resource filter. This should prevent regression of the bug fixed in #48786.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 46738, 48827, 48831) Moving disruption controller e2es to workload/ Based on #45301 Moving to track sig-apps in a single directory cc @kubernetes/sig-contributor-experience-misc @kubernetes/sig-apps-misc @erictune @kow3ns @crimsonfaith91
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue StatefulSet upgrade test - replicated database (mysql) **What this PR does / why we need it**: Adds a new upgrade test. The test creates a statefulset with a replicated mysql database. It populates the database and then continually polls the data while performing an upgrade. Ultimately, this PR increases confidence of reliability during upgrades. It helps show that StatefulSets and Pod Disruption Budgets are doing what they're supposed to. Code to pay attention to this was added for #38336. Also vendors in a golang mysql client driver, for use in the test. **Release note**: ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 48781, 48817, 48830, 48829, 48053) kubeadm: Start to remove old envparams **What this PR does / why we need it**: Historically, the envparams feature was used as a way to easily debug `kubeadm` while developing it in the v1.3-v1.4 timeframe. Since then some parameters have been hanging around and not being moved into the API as they should have. Note: This is a temporary step; moving things into the API. Still, the API is gonna change, this is not the end state. But this is better than keeping the envparams. I'm gonna deal with `KubernetesDir` in the next PR. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # Fixes: kubernetes/kubeadm#326 **Special notes for your reviewer**: **Release note**: ```release-note NONE ``` @timothysc @pipejakob
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 48781, 48817, 48830, 48829, 48053) vSphere for cloud-controller-manager **What this PR does / why we need it**: This is to implement the `NodeAddressesByProviderID` and `InstanceTypeByProviderID` methods for cloud-controller-manager for vSphere cloud provider. Currently vSphere cloud provider only supports VMs in the same folder. Thus `NodeAddressesByProviderID` is similar to `NodeAddresses` with a simple ProviderID to NodeName translation. `InstanceTypeByProviderID` returns nil as same as `InstanceType`. **Which issue this PR fixes** Part of Issue https://github.com/kubernetes/kubernetes/issues/47257 **Release note**: ```NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 48781, 48817, 48830, 48829, 48053) Fix yaml-quote typo Caught this looking through CI logs. /assign wojtek-t
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 48781, 48817, 48830, 48829, 48053) Move kubectl e2e tests to their own directory and prefix the test nam… ```release-note NONE ```
-