- 12 Aug, 2016 40 commits
-
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue [kubelet] Introduce --protect-kernel-defaults flag to make the tunable behaviour configurable Let's make the default behaviour of kernel tuning configurable. The default behaviour is kept modify as has been so far.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Scheduledjob e2e @erictune last element of the scheduledjob puzzle. I think we'll iterate on this once we have all the puzzles in place. This is one of those things that will be allowed to merge after code freeze. ```release-note * Introducing ScheduledJobs as described in [the proposal](https://github.com/kubernetes/kubernetes/blob/master/docs/proposals/scheduledjob.md) as part of `batch/v2alpha1` version (experimental feature). ``` []()
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Avoid unnecessary copies on GCI initialization. The issue I faced was that when starting a cluster I was getting: ``` Aug 12 11:12:46 e2e-test-wojtekt-master configure.sh[1079]: cp: error writing '/home/kubernetes/kubernetes-src.tar.gz': No space left on device ``` This PR reduces amount of space that is needed on startup, as well as this speeds up starting cluster. @lavalamp @dchen1107
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue pkg/kubelet/container: amend cgroup type documentation
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add Node.js `kubernetes-client` to client-libraries.md
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Extend the wait time to 2*time.Minute for liveness check test. Fixes https://github.com/kubernetes/kubernetes/issues/30264. https://github.com/kubernetes/kubernetes/pull/29814 changes the wait time to 1 minute, which is not enough. That's what causes the flake. The test expected the container to be restarted, and the container was indeed restarted but it took about 1 minute: ``` Aug 9 01:03:40.696: INFO: At 2016-08-09 01:02:35 -0700 PDT - event for liveness-exec: {default-scheduler } Scheduled: Successfully assigned liveness-exec to e2e-gce-agent-pr-38-0-minion-group-bv95 Aug 9 01:03:40.696: INFO: At 2016-08-09 01:02:36 -0700 PDT - event for liveness-exec: {kubelet e2e-gce-agent-pr-38-0-minion-group-bv95} Pulled: Container image "gcr.io/google_containers/busybox:1.24" already present on machine Aug 9 01:03:40.696: INFO: At 2016-08-09 01:02:36 -0700 PDT - event for liveness-exec: {kubelet e2e-gce-agent-pr-38-0-minion-group-bv95} Created: Created container with docker id cf4e8e60535e Aug 9 01:03:40.696: INFO: At 2016-08-09 01:02:36 -0700 PDT - event for liveness-exec: {kubelet e2e-gce-agent-pr-38-0-minion-group-bv95} Started: Started container with docker id cf4e8e60535e Aug 9 01:03:40.696: INFO: At 2016-08-09 01:02:55 -0700 PDT - event for liveness-exec: {kubelet e2e-gce-agent-pr-38-0-minion-group-bv95} Unhealthy: Liveness probe failed: Aug 9 01:03:40.696: INFO: At 2016-08-09 01:03:26 -0700 PDT - event for liveness-exec: {kubelet e2e-gce-agent-pr-38-0-minion-group-bv95} Killing: Killing container with docker id cf4e8e60535e: pod "liveness-exec_e2e-tests-container-probe-b1wip(a1f856fc-5e07-11e6-a7e1-42010af00002)" container "liveness" is unhealthy, it will be killed and re-created. Aug 9 01:03:40.696: INFO: At 2016-08-09 01:03:26 -0700 PDT - event for liveness-exec: {kubelet e2e-gce-agent-pr-38-0-minion-group-bv95} Created: Created container with docker id 0b18537dc794 Aug 9 01:03:40.696: INFO: At 2016-08-09 01:03:26 -0700 PDT - event for liveness-exec: {kubelet e2e-gce-agent-pr-38-0-minion-group-bv95} Started: Started container with docker id 0b18537dc794 ``` This PR recovers the wait time to the original 2 * time. Mark P0 to match the corresponding issue. @fejta
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix TestPidOf {procfs} - Take #2 We should not bailout when we get an error. We should continue processing other files/directories. We were returning the err passed in which was causing the processing to stop. Fixes #30377 -
Kubernetes Submit Queue authored
Automatic merge from submit-queue some optimization for server.go The PR modified two places: 1) Optimise the code style according to the go style guide; 2) Optimise the log.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Kubelet: generate sandbox/container config for new runtime API Generate sandbox/container config for new runtime API. Part of #28789 . CC @yujuhong @Random-Liu @dchen1107
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Get version from started.json. <!-- Reviewable:start --> This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/30385) <!-- Reviewable:end -->
-
Kubernetes Submit Queue authored
Merge pull request #30460 from juanvallejo/jvallejo_kube-add-zsh-compatibility-note-kubectl-completion Automatic merge from submit-queue Add zsh compatibility note `completion` cmd help zsh completions are not supported on zsh versions < 5.2. This patch advices user on supported versions of zsh when using the `completion` command to avoid potential UX failure. ##### After `$ kubectl completion -h` ``` Output shell completion code for the given shell (bash or zsh). This command prints shell code which must be evaluation to provide interactive completion of kubectl commands. Examples: $ source <(kubectl completion bash) will load the kubectl completion code for bash. Note that this depends on the bash-completion framework. It must be sourced before sourcing the kubectl completion, e.g. on the Mac: $ brew install bash-completion $ source $(brew --prefix)/etc/bash_completion $ source <(kubectl completion bash) If you use zsh*, the following will load kubectl zsh completion: $ source <(kubectl completion zsh) * zsh completions are only supported in versions of zsh >= 5.2 ``` ```release-note release-note-none ``` <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/30460) <!-- Reviewable:end -->
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue fix mistakes in api_changes.md <!-- Checklist for submitting a Pull Request Please remove this comment block before submitting. 1. Please read our [contributor guidelines](https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md). 2. See our [developer guide](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md). 3. If you want this PR to automatically close an issue when it is merged, add `fixes #<issue number>` or `fixes #<issue number>, fixes #<issue number>` to close multiple issues (see: https://github.com/blog/1506-closing-issues-via-pull-requests). 4. Follow the instructions for [labeling and writing a release note for this PR](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes) in the block below. --> ```release-note fix mistakes in api_changes.md ``` Signed-off-by:
Xianglin Gao <xlgao@zju.edu.cn> <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/30426) <!-- Reviewable:end -->
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Label MemoryEviction [Disruptive] This test has the potential to be disruptive. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/30482) <!-- Reviewable:end -->
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue openstack: Autodetect LBaaS v1 vs v2 ```release-note * openstack: autodetect LBaaS v1/v2 by querying for available extensions. For most installs, this effectively changes the default from v1 to v2. Existing installs can add "lb-version = v1" to the provider config file to continue to use v1. ``` <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/29726) <!-- Reviewable:end -->
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add support for kube-up.sh to deploy Calico network policy to GCI masters Also remove requirement for calicoctl from Debian / salt installed nodes and clean it up a little by deploying calico-node with a manifest rather than calicoctl. This also makes it more reliable by retrying properly. How to use: ``` make quick-release NETWORK_POLICY_PROVIDER=calico cluster/kube-up.sh ``` One place where I was uncertain: - CPU allocations (on the master particularly, where there's very little spare capacity). I took some from etcd, but if there's a better way to decide this, I'm happy to change it. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/29037) <!-- Reviewable:end -->
-
Maciej Szulik authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Update HumanResourcePrinter signature w single PrintOptions param release-note-none - Makes [HumanReadablePrinter options field non-exported again](https://github.com/kubernetes/kubernetes/blob/master/pkg/kubectl/resource_printer.go#L346-349) - Adds test-case for HumanReadablePrinter resource printing with aliases. - Better formatting for saving resource "kind" aliases []() <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/28509) <!-- Reviewable:end -->
-
Tamer Tas authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Implement 'kubectl top' command ```release-note Added 'kubectl top' command showing the resource usage metrics. ``` Sample output: Nodes: ``` $ kubectl top node NAME CPU MEMORY STORAGE TIMESTAMP kubernetes-minion-group-xxxx 76m 1468 Mi 0 Mi Tue, 12 Jul 2016 17:37:00 +0200 kubernetes-minion-group-yyyy 73m 1511 Mi 0 Mi Tue, 12 Jul 2016 17:37:00 +0200 kubernetes-minion-group-zzzz 46m 1506 Mi 0 Mi Tue, 12 Jul 2016 17:37:00 +0200 kubernetes-master 76m 2059 Mi 0 Mi Tue, 12 Jul 2016 17:37:00 +0200 ``` Pods in all namespaces: ``` $ kubectl top pod --all-namespaces NAMESPACE NAME CPU MEMORY STORAGE TIMESTAMP default nginx-1111111111-zzzzz 0m 1 Mi 0 Mi Tue, 12 Jul 2016 17:49:00 +0200 kube-system etcd-server-kubernetes-master 4m 116 Mi 0 Mi Tue, 12 Jul 2016 17:49:00 +0200 kube-system fluentd-cloud-logging-kubernetes-minion-group-xxxx 14m 110 Mi 0 Mi Tue, 12 Jul 2016 17:49:00 +0200 kube-system kube-dns-v18-zzzzz 1m 6 Mi 0 Mi Tue, 12 Jul 2016 17:49:00 +0200 ... ``` Pod with containers: ``` $ kubectl top pod heapster-v1.1.0-1111111111-miail --namespace=kube-system --containers NAMESPACE NAME CPU MEMORY STORAGE TIMESTAMP kube-system heapster-v1.1.0-1111111111-miail 1m 42 Mi 0 Mi Tue, 12 Jul 2016 17:52:00 +0200 heapster 1m 26 Mi 0 Mi eventer 0m 3 Mi 0 Mi heapster-nanny 0m 6 Mi 0 Mi eventer-nanny 0m 6 Mi 0 Mi ``` ref #11382 []() <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/28844) <!-- Reviewable:end --> -
Kubernetes Submit Queue authored
Automatic merge from submit-queue return err on `kubectl run --image` with invalid value When running `kubectl run <configname> --image="Invalid$$%ImageValue%%__"`, a configuration is successfully created with an image name that is not a valid value for an image reference. This patch validates that the image name is a valid image reference, and returns an error before creating a config if an invalid value is passed. `$ kubectl run test --image="Invalid__%imagename"` ``` error: Invalid image name "Invalid__%imagename": invalid reference format ``` <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/30162) <!-- Reviewable:end -->
-
Wojciech Tyczynski authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Basic audit log Fixes #2203 by introducing simple audit logging, including the information about impersonation. We currently have something identical in openshift, but I'm open to any suggestions. Sample logs look like that: as `<self>`: ``` AUDIT: id="75114bb5-970a-47d5-a5f1-1e99cea0574c" ip="127.0.0.1" method="GET" user="test-admin" as="<self>" namespace="openshift" uri="/api/v1/namespaces/openshift/pods/python" AUDIT: id="75114bb5-970a-47d5-a5f1-1e99cea0574c" response=200 ``` as user: ``` AUDIT: id="b0a443ae-f7d8-408c-a355-eb9501fd5c59" ip="192.168.121.118" method="GET" user="system:admin" as="test-admin" namespace="openshift" uri="/api/v1/namespaces/openshift/pods/python" AUDIT: id="b0a443ae-f7d8-408c-a355-eb9501fd5c59" response=200 ``` ```release-note * Add basic audit logging ``` @ericchiang @smarterclayton @roberthbailey @erictune @ghodss []() <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/27087) <!-- Reviewable:end -->
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add an issue template, tighten PR template Supersedes #28488 <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/30167) <!-- Reviewable:end -->
-
Marcin Wielgus authored
Federation e2e test util using clientset 1.4
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fixed misconfigured kubelet on containervm image for node-e2e. Fixed #30412 to unblock @coufon's performance benchmark work. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/30415) <!-- Reviewable:end -->
-
Maciej Szulik authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Avoid computing DeepEqual in controllers all the time Computing DeepCopy was responsible for ~33% of cpu usage of controller-manager before this PR. <!-- Checklist for submitting a Pull Request Please remove this comment block before submitting. 1. Please read our [contributor guidelines](https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md). 2. See our [developer guide](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md). 3. If you want this PR to automatically close an issue when it is merged, add `fixes #<issue number>` or `fixes #<issue number>, fixes #<issue number>` to close multiple issues (see: https://github.com/blog/1506-closing-issues-via-pull-requests). 4. Follow the instructions for [labeling and writing a release note for this PR](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes) in the block below. --> ```release-note * Use the release-note-* labels to set the release note state * Clear this block to use the PR title as the release note -OR- * Enter your extended release note here (newlines are formatted as bullets) ``` <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/30277) <!-- Reviewable:end -->
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue cluster/log-dump scp shouldn't check host keys for aws parity with cluster/aws/util.sh:ssh-to-node <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/30472) <!-- Reviewable:end -->
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Let kubectl delete rc and rs with DeleteOptions.OrphanDependents=false so that when the garbage collector is enabled, RC and RS are deleted immediately without waiting for the garbage collector to orphan the pods. There is no user visible changes, so we don't need a release note. cc @fabioy <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/30461) <!-- Reviewable:end -->
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Marked NodePhase deprecated. cc/ @lavalamp Even Kubernetes stops set NodePhase for a while, the user might patch NodeStatus with NodePhase. Marked the field deprecated and documented first. xref: https://github.com/kubernetes/kubernetes.github.io/pull/549 <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/30005) <!-- Reviewable:end -->
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue t.Errorf output wrong variables in identity_mapper_test.go t.Errorf output wrong variables in identity_mapper_test.go <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/29502) <!-- Reviewable:end -->
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue hack/e2e.go: Make --dump run if --up fails, and if --down isn't specified See https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-aws/629 for why this would be useful. (And the requirement for --down is just unnecessary AFAICT.) <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/30405) <!-- Reviewable:end -->
-
Marcin Wielgus authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix some typos in control-plane-resilience.md Fix some typos in control-plane-resilience.md <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/30209) <!-- Reviewable:end -->
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Name jobs created by sj deterministically ```release-note Name the job created by scheduledjob (sj) deterministically with sj's name and a hash of job's scheduled time. ``` @erictune @soltysh <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/30420) <!-- Reviewable:end -->
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Turn on flake mitigation for the node e2e test <!-- Reviewable:start --> This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/30485) <!-- Reviewable:end -->
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix code generators-- make scheme building composable I needed to make some changes to make my other refactoring possible and this got rather large. We now provide a "SchemeBuilder" to help all of the api packages provide their scheme-building functions (addKnownTypes and friends) in a standardized way. This also allows generated deepcopies & conversions to be entirely self contained, the project will now build without them being present (as they can add themselves to the SchemeBuilder). (Although if you actually build without them, you will get reduced performance!) Previously, there was no way to construct your own runtime.Scheme (e.g., to test), you had to use the api.Scheme object, which has all sorts of non-hermetic cruft in it. Now you can get everything from a package by calling the scheme builder's AddToScheme, including the generated functions, if they are present. Next steps are to allow for declaring dependencies, and to standardize the registration & install code. (#25434) <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/25526) <!-- Reviewable:end -->
-
Silas Boyd-Wickizer authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue the observed usage should match those that have hard constraints in the sync process, the quota will be replenished, the new observed usage will be sumed from each evaluator, if the previousUsed set is not be cleared, the new usage will be dirty, maybe some unusage resource still in , as the code below newUsage = quota.Mask(newUsage, matchedResources) for key, value := range newUsage { usage.Status.Used[key] = value } so i think here shoul not set value previousUsed <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/29653) <!-- Reviewable:end --> -
Pengfei Ni authored
-