- 15 Sep, 2016 4 commits
-
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Do not report warning event when an unknown deleter is requested When Kubernetes does not have a plugin to delete a PV it should wait for either external deleter or storage admin to delete the volume instead of throwing an error. This is the same approach as in #32077 @kubernetes/sig-storage
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Etcd3 v3client + grpc client leak fix This re-enables the client and plumbs through the destroyFunc to cleanup clients. Fix for https://github.com/kubernetes/kubernetes/issues/31262
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue AWS: Reduce frequency of volume-mount poll
-
Saad Ali authored
fully verify client-gen in verification tests
-
- 14 Sep, 2016 36 commits
-
-
Mike Danese authored
-
Mike Danese authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue To improve error messages, validate the existence of a namespace. Fixes #15542 @deads2k @kubernetes/kubectl
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fixed #32366: wrong master pd name during kube-down.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Make it possible to run local kubelet independently of cluster Makes it possible to start a cluster and kubelet independently (was necessary when debugging issues related to restarting kubelet for existing node).
-
Justin Santa Barbara authored
When we are mounting a lot of volumes, we frequently hit rate limits. Reduce the frequency with which we poll the status; introduces a bit of latency but probably matches common attach times pretty closely, and avoids causing rate limit problems everywhere. Also, we now poll for longer, as when we timeout, the volume is in an indeterminate state: it may be about to complete. The volume controller can tolerate a slow attach/detach, but it is harder to tolerate the indeterminism. Finally, we ignore a sequence of errors in DescribeVolumes (up to 5 in a row currently). So we will eventually return an error, but a one off-failure (e.g. due to rate limits) does not cause us to spuriously fail.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue plugin/pkg: add ericchiang to owners for OpenID Connect plugins On the CoreOS side I'm taking over these components. @erictune has suggested `pkg/registry/{cluster}role{binding}s/OWNERS` as well but I'd feel more comfortable as a reviewer for those specific parts of RBAC for a couple more cycles since @liggitt and @deads2k have had way more experience in the registry code. Beyond that the only existing OWNERS files for auth are `pkg/auth/OWNERS` and `plugin/pkg/auth/OWNERS` both of which include @liggitt and @erictune. There's also nothing in the `plugin/pkg/client` path. I'm a little unclear on the implications for future PRs that are assigned to me (e.g. webhook or RBAC reviews). cc @kubernetes/sig-auth -
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix clientcmd for a non-host cluster client running in a pod. This is based on @errordeveloper's PR #32438. It fixes a case where default config is invalid and original config, i.e. `mergedConfig` is empty. It also adds a test for the case where default config is invalid and original config is neither invalid nor empty. cc @errordeveloper @kubernetes/sig-cluster-federation @pwittrock @colhom
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Docker digest validation is too strict Docker 1.10 does not guarantee that the pulled digest matches the digest on disk when dealing with v1 schemas stored in a Docker registry. This is the case for images like centos/ruby-23-centos7@sha256:940584acbbfb0347272112d2eb95574625c0c60b4e2fdadb139de5859cf754bf which as a result of #30366 cannot be pulled by Kube from a Docker 1.10 system. This partially reverts commit 875fd16e.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix printing container usage in kubectl top **What this PR does / why we need it**: Fix a bug in kubectl top, which showed the same value of usage for all containers in a pod. **Release note**: ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Vendor github.com/square/go-jose for kubeadm and kube-discovery **What this PR does / why we need it**: This is to be used by `kubeadm` (#31221) and @dgoodwin's `kube-discovery` (PR pending). ***[xref kubernetes/features#11]*** ***[cc @kubernetes/sig-cluster-lifecycle]*** **Special notes for your reviewer**: This is first time I've used `godep`, so please verify if all is quite right about the diff. I'm not 100% sure if there should be secondary dependencies or not. ```release-note NONE ```
-
Clayton Coleman authored
Docker 1.10 does not guarantee that the pulled digest matches the digest on disk when dealing with v1 schemas stored in a Docker registry. This is the case for images like centos/ruby-23-centos7@sha256:940584acbbfb0347272112d2eb95574625c0c60b4e2fdadb139de5859cf754bf which as a result of #30366 cannot be pulled by Kube from a Docker 1.10 system. Instead, use RepoDigests field as the primary match, validating the digest, and then fall back to ID (also validating the match). Adds more restrictive matching.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Update Google Cloud API client import paths
-
Ilya Dmitrichenko authored
This is to be used by kubeadm (#31221) and kube-discovery. It adds dummy code to make verification scripts pass. [xref kubernetes/features#11]
-
Brendan Burns authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Make networking tests work reasonably fast in large clusters @bprashanth - FYI
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Create a flag for route reconciliation and deprecate unused node-sync-… cc @pwittrock to decide if it can go in 1.4. It's a zero risk cleanup, that will reduce confusion about cluster configuration.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Allow to use GetSigner with vagrant provider In order to run tests that require ssh access to a node on vagrant we need to provide path to private ssh key. Now it will be possible to do using VAGRANT_SSH_KEY environment variable
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Ignore staging folder in update gofmt small bugfix in hack/update-gofmt.sh
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue add break may be better in the loop
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue kubectl: run validation for 'top pod' @mksalawa @kubernetes/kubectl
-
Timothy St. Clair authored
During etcd3.clientv3 integration we had discovered we were leaking connections
-
Timothy St. Clair authored
This reverts commit 9dcef2e3.
-
Jerzy Szczepkowski authored
Fixed #32366: wrong master pd name during kube-down.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Recombine the condition for the "shouldScale" function The PR recombine the condition for the "shouldScale" function, abstract the common condition(hpa.Status.LastScaleTime == nil).
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue etcd: data rollback tool of v3 -> v2 ref: https://github.com/kubernetes/features/issues/44 ref #20504 What? This provides a rollback tool for some users to rollback etcd data from v3 to v2.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Get image and machine info from apiserver in node e2e test This PR changes node e2e test to get image and machine information from API server instead of pass them from Jenkins test framework. The original format to pass image and machine info is naming the test node as "machine-image-uuid", which is hard to parse because "-" occurs a lot in both machine and image names. Now we add two labels "image" and "machine" into performance data. The machine type has the format "cpu:1core,memory:3.6GB". This PR is based on #32250.
-
Wojciech Tyczynski authored
-
mksalawa authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Improving StopContainer failed log level Using at least Warning level will be more property
-
gmarek authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Bumped Heapster to v1.2.0 ```release-note Bumped Heapster to v1.2.0. More details about the release https://github.com/kubernetes/heapster/releases/tag/v1.2.0 ``` Version `v1.2.0` is a stable release of the previous release candidate `v1.2.0-beta.3`. The only difference is bumped Kubernetes deps to the lastest stable release `v1.4.0-beta.3` https://github.com/kubernetes/heapster/pull/1290. It's low risk change. It may impact HPA and Monitoring e2e tests.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Move nginx ingress e2e to slow Normal GCE L7 e2e takes ~15m and runs in a feature private suite. This e2e ensure that the api isn't broken, by creating an nginx controller. I plan to write a really slimmed down version for presubmit, but I need to shave off a minute to get it below 5m. Fixes https://github.com/kubernetes/kubernetes/issues/23416
-
Piotr Szczesniak authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue kubectl version -c has been deprecated, use --client instead ``` Flag shorthand -c has been deprecated, please use --client instead. ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add test for --quiet flag for kubectl run This adds a test for the changes introduced in #30247 and #28801. Ref #28695
-