- 18 Feb, 2017 4 commits
-
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 41649, 41658, 41266, 41371, 41626) Split request node certificate Split the `RequestNodeCertificate` function so the behavior can also be used by non-node callers.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 41649, 41658, 41266, 41371, 41626) Allow `build/run.sh make help` to run **What this PR does / why we need it**: typo fix; `build/run.sh make help` doesn't work for me on OS X w/ docker 1.13.x, this PR fixes that **Release note**: ```release-note NONE ``` /cc @spxtr
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 41649, 41658, 41266, 41371, 41626) Fix cronjob controller panic on status update failure #41655 @kubernetes/sig-apps-bugs @soltysh @erictune
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Mark cluster logging tests for Stackdriver flaky Disable Stackdriver cluster logging tests until https://github.com/kubernetes/kubernetes/issues/41647 is resolved
-
- 17 Feb, 2017 34 commits
-
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue fix kubectl create configmap help messages Signed-off-by:bruceauyeung <ouyang.qinhua@zte.com.cn> **What this PR does / why we need it**: 1. the first example command actually doesn't specify any keys. i think `with keys for each file` is incorrect. 2. `names on disk` is confusing. in usage the word `NAME` means configmap, so i think it's better saying `file basenames on disk` 3. in this context, `--from-file` can be specified multiple times, but in each occurance only one key file can be specified, besides we should keep consistent with the later case (key is specified). so i changed words in this sentence to singular. and to avoid confusing, i use `key` instead of `name`
-
Janet Kuo authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Added a basic monitor for providing etcd version related info Fixes #41071 This tool scrapes metrics partly from etcd's /version and /metrics endpoints and partly using etcdctl and exposes them as prometheus metrics at `http://localhost:9101/metrics` endpoint on the master. Here is a summary of the metrics it exposes (self-explanatory from the code): - etcdVersionFetchCount = prometheus.NewCounterVec( prometheus.CounterOpts{ Namespace: "etcd", Name: "version_info_fetch_count", Help: "Number of times etcd's version info was fetched, labeled by etcd's server binary and cluster version", }, []string{"serverversion", "clusterversion"}) - etcdGRPCRequestsTotal = prometheus.NewCounterVec( prometheus.CounterOpts{ Namespace: namespace, Name: "grpc_requests_total", Help: "Counter of received grpc requests, labeled by grpc method and grpc service names", }, []string{"grpc_method", "grpc_service"}) For further info on how to run this as a binary/docker-container/kubernetes-pod and checking the metrics, have a look at the README.md file. cc @fgrzadkowski @wojtek-t @piosz
-
Mik Vyatskov authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Switch service controller to shared informers Originally part of #40097 cc @deads2k @smarterclayton @gmarek @wojtek-t @timothysc @sttts @liggitt @kubernetes/sig-scalability-pr-reviews
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Expose storage media type as env variable Ref #40636 @mml
-
Jacob Simpson authored
Split the `RequestNodeCertificate` function so it can be called with different arguments.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 41604, 41273, 41547) remove validNonResourceVerbs in create role non-resource-url is only reasonable for clusterroles
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 41604, 41273, 41547) Switch pv controller to shared informer This is WIP because I still need to do something with bazel? and add 'get storageclasses' to the controller-manager rbac role @jsafrane PTAL and make sure I did not break anything in the PV controller. Do we need to clone the volumes/claims we get from the shared informer before we use them? I could not find a place where we modify them but you would know for certain. cc @ncdc because I copied what you did in your other PRs.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Reduce default value of kubemark's NUM_NODES to 10 Changing the default value of kubemark's NUM_NODES from 100 to 10, as it would then be possible to start kubemark on gce clusters that have been started using kube-up that uses the default config of three n1-standard-2 nodes. I've already been asked by a couple of people about why kubemark is not starting on their cluster because of this. More people shouldn't be facing this issue in future. cc @kubernetes/sig-scalability-misc @wojtek-t @gmarek
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add cluster logging load test for GCL Changed code around logging tests a little to avoid duplication. Added GCL go library, because command line tool cannot handle required number of logs effectively. Related to https://github.com/kubernetes/kubernetes/issues/34310 @piosz
-
Wojciech Tyczynski authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 41548, 41221) StatefulSet Upgrade Test Adds StatefulSet upgrade tests and moves common functionality into the framework package. This removes the potential for cyclic dependencies while allowing for code reuse. ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 41548, 41221) hack/*.sh: re-add staging dirs to verify+update scripts
-
Shyam Jeedigunta authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 41606, 41475) Added e2e upgrade test for Horizontal Pod Autoscaler.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 41606, 41475) Modify kubemark run-e2e-tests.sh to run right command based on environment In order to run-e2e-tests.sh in kubemark, we currently need to toggle comment b/w the last 2 lines of the script. This is inconvenient to change each time and sometimes this change gets accidentally included as part of a PR. It's even difficult for someone newly trying kubemark to figure this out in order to run tests. Changed the logic to use the right command based on whether the script is running from within a docker container or just locally. cc @kubernetes/sig-scalability-misc @wojtek-t @gmarek
-
Mik Vyatskov authored
-
Mik Vyatskov authored
-
Jerzy Szczepkowski authored
Added e2e upgrade test for Horizontal Pod Autoscaler.
-
Dr. Stefan Schimanski authored
-
Dr. Stefan Schimanski authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Improve code coverage for pkg/api/util **What this PR does / why we need it**: Improve code coverage for pkg/api/util . Thanks. **Special notes for your reviewer**: **Release note**: ```release-note ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 41517, 41494, 41163) Deployment: filter out old RSes that are deleted or with non-zero replicas before cleanup Fixes #36379 cc @zmerlynn @yujuhong @kargakis @kubernetes/sig-apps-bugs
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 41517, 41494, 41163) Make scheduler_perf warn rather then fail if scheduling rate is betwe… **What this PR does / why we need it** Fix scheduler per bench tests so they pass even if there is a cold interval . **Special notes for your reviewer**: This wont effect CI, as this bench test is run manually by devs.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue update-bazel.sh to treat GOPATH as a path
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue only construct shortcutmapper when we have the discovery client Resource shortnames come from the discoveryclient, so we should only wrap with that mapper when we have the information we need.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add SIG owners to e2e tests **What this PR does / why we need it**: Adds SIG owners to e2e tests in order to support assigning test flakes and general test failures to SIGs rather than relying solely on individuals. Ideally this will help spread the maintenance burden across more This work is part of closing https://github.com/kubernetes/contrib/issues/2389 **Which issue this PR fixes** Part of the work to address - https://groups.google.com/forum/#!topic/kubernetes-dev/5kTLRfKId9g Tracking issue - https://github.com/kubernetes/contrib/issues/2389 **Special notes for your reviewer**: None **Release note**: `NONE`.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 40505, 34664, 37036, 40726, 41595) Allow `make test-integration` to pass on OSX **What this PR does / why we need it**: `make test-integration` isn't passing on my OSX setup (10.11.6, go1.7, docker 1.13.1). Tests that startup an api server fail because the default `cert-dir` of `/var/run/kubernetes` isn't world-writable. Use a tempdir instead. **Release note**: ```release-note NONE ``` /cc @kubernetes/sig-testing-pr-reviews
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 40505, 34664, 37036, 40726, 41595) Rename provisioner config struct
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 40505, 34664, 37036, 40726, 41595) dockertools: call TearDownPod when GC-ing infra pods The docker runtime doesn't tear down networking when GC-ing pods. rkt already does so make docker do it too. To ensure this happens, infra pods are now always GC-ed rather than gating them by containersToKeep. This prevents IPAM from leaking when the pod gets killed for some reason outside kubelet (like docker restart) or when pods are killed while kubelet isn't running. Fixes: https://github.com/kubernetes/kubernetes/issues/14940 Related: https://github.com/kubernetes/kubernetes/pull/35572
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 40505, 34664, 37036, 40726, 41595) filter lastAppliedConfig annotation for describe secret Temporarily addresses: #23564. This patch filters out the lastAppliedConfig annotation when describing a secret. ```release-note kubectl describe no longer prints the last-applied-configuration annotation for secrets. ```
-
xilabao authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Extract strings from the rollout command. @fabianofranz @kubernetes/sig-cli-pr-reviews
-
- 16 Feb, 2017 2 commits
-
-
Shyam Jeedigunta authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 38101, 41431, 39606, 41569, 41509) kubeadm: Reorder the token packages more logically **What this PR does / why we need it**: In order to be able to implement https://github.com/kubernetes/kubernetes/pull/41417, the token functionality (which now is spread across the codebase), should be in two places: a generic token functions library, which in the future _may_ [move into client-go](https://github.com/kubernetes/kubernetes/pull/41281#discussion_r101357106) in some form, and a package for the token handling against the api server. This commit has no large functional changes. ``` kubeadm: Aggregate the token functionality in sane packages. - Factor out token constants to kubeadmconstants. - Move cmd/kubeadm/app/util/{,token/}tokens.go - Use the token-id, token-secret, etc constants provided by the bootstrapapi package - Move cmd/kubeadm/app/master/tokens.go to cmd/kubeadm/app/phases/token/csv.go This refactor basically makes it possible to hook up kubeadm to the BootstrapSigner controller later on ``` **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 ``` @mikedanese @pires @errordeveloper @dmmcquay @jbeda @GheRivero
-