- 04 Aug, 2016 20 commits
-
-
gmarek authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Enable PodAffinity by default in scheduler Ref #26144 @gmarek - FYI
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Resolve docker-daemon cgroup issue for both systemd and non-systemd node for node e2e tests Fixed https://github.com/kubernetes/kubernetes/issues/29827 cc/ @coufon this should unblock your pr: #29764 I validated both containervm image and coreos image, and works as expected. This is also required for adding gci image to node e2e test infrastructure.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix deployment e2e test: waitDeploymentStatus should error when entering an invalid state Follow up #28162 1. We should check that max unavailable and max surge aren't violated at all times in e2e tests (didn't check this in deployment scaled rollout yet, but we should wait for it to become valid and then continue do the check until it finishes) 2. Fix some minor bugs in e2e tests @kubernetes/deployment
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Remove myself from test ownership. These are almost certainly not correct, but probably more likely owners than myself. @rmmh @dchen1107 @timstclair @erictune @mtaufen @caesarxuchao @fgrzadkowski @krousey @lavalamp
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add dry run capability to cherry_pick_pull.sh When creating patches for downstream projects like OpenShift, I found it to be helpful to have a dry run mode for the cherry-pick script. @k8s-oncall cc @kubernetes/rh-cluster-infra
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue convert README.md to doc.go It seems the convention is to use a doc.go, not a README.md. I needed to work around this README.md when in #29147, see https://github.com/kubernetes/kubernetes/pull/29147#discussion-diff-73239124R73.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Verify if Secure and InsecurePort are equal for apiserver If we specify the kube-apiserver flags `--secure-port` and `--insecure-port` with the same port, the server will print the below error info repeatedly. In fact, it's meaningless to do this. It should verify if the two flags are equal. If so, the server should give error info and exit directly. ``` root@vm:~# [restful] 2016/08/01 13:11:52 log.go:30: [restful/swagger] listing is available at https://172.16.1.11:8888/swaggerapi/ [restful] 2016/08/01 13:11:52 log.go:30: [restful/swagger] https://172.16.1.11:8888/swaggerui/ is mapped to folder /swagger-ui/ E0801 13:11:53.102232 2481 genericapiserver.go:733] Unable to listen for secure (listen tcp 0.0.0.0:8888: bind: address already in use); will try again. E0801 13:12:08.116463 2481 genericapiserver.go:733] Unable to listen for secure (listen tcp 0.0.0.0:8888: bind: address already in use); will try again. ``` After fixing, the print is like this: ``` root@vm:~# F0801 11:51:44.308180 1921 genericapiserver.go:599] --secure-port and --insecure-port cannot use the same port. goroutine 1 [running]: k8s.io/kubernetes/vendor/github.com/golang/glog.stacks(0x4871d00, 0x0, 0x0, 0x0) /home/paas/zxp/code/k8s/fork/kubernetes/_output/local/go/src/k8s.io/kubernetes/vendor/github.com/golang/glog/glog.go:766 +0xb8 k8s.io/kubernetes/vendor/github.com/golang/glog.(*loggingT).output(0x48517c0, 0xc800000003, 0xc820368000, 0x470aeab, 0x13, 0x257, 0x0) /home/paas/zxp/code/k8s/fork/kubernetes/_output/local/go/src/k8s.io/kubernetes/vendor/github.com/golang/glog/glog.go:717 +0x259 k8s.io/kubernetes/vendor/github.com/golang/glog.(*loggingT).printf(0x48517c0, 0xc800000003, 0x3518280, 0x3b, 0x0, 0x0, 0x0) /home/paas/zxp/code/k8s/fork/kubernetes/_output/local/go/src/k8s.io/kubernetes/vendor/github.com/golang/glog/glog.go:655 +0x1d4 k8s.io/kubernetes/vendor/github.com/golang/glog.Fatalf(0x3518280, 0x3b, 0x0, 0x0, 0x0) /home/paas/zxp/code/k8s/fork/kubernetes/_output/local/go/src/k8s.io/kubernetes/vendor/github.com/golang/glog/glog.go:1145 +0x5d k8s.io/kubernetes/pkg/genericapiserver.verifySecureAndInsecurePort(0xc820132800) /home/paas/zxp/code/k8s/fork/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/genericapiserver/genericapiserver.go:599 +0xad k8s.io/kubernetes/pkg/genericapiserver.ValidateRunOptions(0xc820132800) /home/paas/zxp/code/k8s/fork/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/genericapiserver/genericapiserver.go:607 +0x4b k8s.io/kubernetes/pkg/genericapiserver.DefaultAndValidateRunOptions(0xc820132800) /home/paas/zxp/code/k8s/fork/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/genericapiserver/genericapiserver.go:611 +0x4e k8s.io/kubernetes/cmd/kube-apiserver/app.Run(0xc8202c9560, 0x0, 0x0) /home/paas/zxp/code/k8s/fork/kubernetes/_output/local/go/src/k8s.io/kubernetes/cmd/kube-apiserver/app/server.go:84 +0x8e main.main() /home/paas/zxp/code/k8s/fork/kubernetes/_output/local/go/src/k8s.io/kubernetes/cmd/kube-apiserver/apiserver.go:48 +0x111 [2]+ Exit 255 ``` This will fix the same issue of federation-apiserver. cc @lavalamp @quinton-hoole
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Modify some detail information in contributing workflow "Compare and pull request" is "Compare & pull request" actually.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue In cluster scripts correct gcloud list arg from '--zone' to '--zones' I started getting these messages when doing `kube-up` and similar operations: WARNING: Abbreviated flag [--zone] will be disabled in release 132.0.0, use the full name [--zones]. This PR corrects the flag where used. Note there are many uses of `--zone` on commands like `gcloud instances describe` which are still correct - those commands do not accept multiple zones. -
Kubernetes Submit Queue authored
Automatic merge from submit-queue automation.md: update lgtm point ref: https://github.com/kubernetes/contrib/pull/1428#issuecomment-237025536
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue libvirt_coreos: to remove old skydns fork fetching from addons @thockin @girishkalele ref https://github.com/kubernetes/kubernetes/pull/29720. Goal of this PR is: - to remove obsolete DNS config files. - to propose a way to fetch the real template As soon https://github.com/kubernetes/kubernetes/pull/29720 will be merged I'm OK to modify this accordingly. FYI: @lhuard1A
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Token review endpoint Unrevert of #28788, which was rolled back because of https://github.com/kubernetes/kubernetes/issues/29375 @cjcullen @wojtek-t I'd like to remerge if possible. Have we gotten the field checking mentioned here relaxed? https://github.com/kubernetes/kubernetes/pull/28788#discussion_r71918442
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Check all places to break the loop when object found Check all places to break the loop when object found.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue VSAN support for VSphere Volume Plugin This PR does the following, - Fixes #28625 (VSphere Volume doesn't unmount): modified vmdk namespace path parsing so it accurately handles VMs in folders. See file pkg/volume/vsphere_volume/vsphere_volume.go. - Updates vmware/govmomi dependency. It was quite behind. The majority of files in the change are in this category. - Adds support for VSAN datastore. Handle namespace to uuid mapping to assist unmount and detach in VSAN case as well. See file pkg/cloudprovider/providers/vsphere/vsphere.go. Tested: - Created a K8s cluster on VSphere with VSAN datastore. Created a vmdk in VSAN datastore and created pod which uses this vmdk. Before fix (VSphere Volume doesn't unmount) it failed. After fix the volume gets successfully unmounted and detached. - Created a K8s cluster on VSphere with VMFS datastore. Created a vmdk in subdirectory of root in VMFS datastore and created pod which uses this vmdk. Before fix (VSphere Volume doesn't unmount) it failed. After fix the volume gets successfully unmounted and detached. -
lixiaobing10051267 authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix 29992 Fix #29992. I copied RC test code to the wrong place to the RS test in #29798. I took a look at the failure reports, they were all failed on the RS test, so #29798 itself is correct. Marked as P2 since it fixes a test flake that will block everyone.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue e2e-runner: Fix the logic of pulling GCI builtin version of k8s Apparently setting JENKINS_PUBLISHED_VERSION didn't work because it only worked with `ci/latest`, `release/latest-1.3` or the like, whereas we wanted to pull specific versions like `release/v1.3.3`. Added a function `fetch_gci_version_tars` instead. @spxtr Can you review? Hopefully this should get our QA tests passing.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Revert "Revert "Drop support for --gce-service-account, require activated creds"" Reverts kubernetes/kubernetes#29242
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Consolidating image pulling logic Moving image puller logic into image manager by consolidating 2 pullers into one implementation.
-
- 03 Aug, 2016 20 commits
-
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue CRI: rename DeletePodSandbox to RemovePodSandbox
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue add DefaultServiceNodePortRange const The PR add DefaultServiceNodePortRange const in server_run_options.go, and use it in genericapiserver.go and server_run_options.go.
-
Chao Xu authored
-
Abrar Shivani authored
- Fix unmount for vsanDatastore - Add support for vsan datastore
-
Yu-Ju Hong authored
This makes it consistent with other calls (e.g., RemoveContainer, RemoveImage).
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Limit number of pods spawned in SchedulerPredicates validates resourc… Fixes https://github.com/kubernetes/kubernetes/issues/29190, With this patch test should spawn at most 10 pods on the smallest node.
-
David McMahon authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Addresses vSphere Volume Attach limits This PR resolves bug #29878.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Move non-Minikube local cluster guides from docs repo to kubernetes d… Move the local cluster docs out of the docs repo. Keeping them around since they may be used by some folks for development.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Federation - common libs - FederatedInformer Fixes #29383 Will add more tests after the first pass of the review. ref: #29347 cc: @nikhiljindal @wojtek-t
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix various typos in kubectl
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Increase the unit test coverage in pkg/util These are easy to test, so lets increase coverage.
-
Chao Xu authored
-
Daniel Smith authored
Use format instead of awk to extract active account/project
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue fix creating pod from file failure in scheduler-predicates fix #29816 ref https://github.com/kubernetes/kubernetes/pull/25584#discussion_r73349738 and https://github.com/kubernetes/kubernetes/pull/25584#discussion_r73349328
-
Hongchao Deng authored
-
Phillip Wittrock authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix elasticsearch example volume descriptors fixes #26257 []()
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue integration test: Modify PVs/PVCs during binding. Previous volume binder code was not able to cope with PVs or PVCs getting modified during the binding process. Current one should be resilient to these changes, so let's test it. It makes the test approximately twice as long as before, from ~2 seconds to ~4-5. @kubernetes/sig-storage Marking as 1.3 target, however it does not really matter here, it's just a test.
-
Ron Lai authored
-