Automatic merge from submit-queue
Use kube-system namespace
Fixes#23153.
Sadly, kube-system isn't automatically created, so people need to make
sure to create it in their turnup scripts. Also after creating
kube-system it can take 10+ seconds for master and proxy to show up.
I tested the equivalent of these changes locally, but not these changes
themselves as I don't have a dev/build env up, so please read carefully
and maybe try them out!
Automatic merge from submit-queue
use single writer to improve quota performance
Performance improvement is comparable to https://github.com/openshift/origin/pull/6658, though I'm getting some crazy stalls during initial calculation on master (not on this branch), so there may be an existing problem. This implementation won't scale out quite as well, but I don't think we'll need much more for a while and this one is easier to read.
This buckets based on namespace, then bunches updates where possible to avoid request fanout, and does fast notification when it can. It correctly handles updating multiple quota docs.
@derekwaynecarr @kubernetes/rh-cluster-infra
Automatic merge from submit-queue
Make detect-node-names less brittle for G{C,K}E
Use the `--format='value()'` option with `gcloud compute instance-groups managed list{,-instances}` instead of `--format=yaml` with a series of `grep`s and `cut`s. This is hopefully a bit more stable.
Fixes#24120.
cc @kubernetes/sig-testing @jlowdermilk @freehan
Automatic merge from submit-queue
rkt: Pass through os argument
This was lost in a rebase in #24496 and, while not required to build, is
required to function correctly under rkt (else panics!)
cc @yifan-gu
Automatic merge from submit-queue
gke-large-cluster: Allow up to 1% of 1000 = 10 nodes
Per 2016/03/16 GKE release note, CreateCluster can return success with
only 99% success.
Automatic merge from submit-queue
Incorrect attribute - docs - pod-security-context
Pod definition had incorrect spelling on attribute `securityContext`
Also fixed the flow of Motivation introduction paragraph.
Automatic merge from submit-queue
Add Subresource & Name to webhook authorizer.
Pass through the Subresource and Name fields from the `authorization.Attributes` to the `SubjectAccessReviewSpec.ResourceAttributes`.
Automatic merge from submit-queue
Refactor image related functions to use docker engine-api
ref #23563
Hopes can do some help, cc @Random-Liu
If it's ok, will add more work here.
Automatic merge from submit-queue
rkt: Return `FinishedAt` for pod
This is implemented via touching a file on stop as a hook in the systemd
unit. The ctime of this file is then used to get the `finishedAt` time
in the future.
In addition, this changes the `startedAt` and `createdAt` to use the api
server's results rather than the annotations it previously used.
It's possible we might want to move this into the api in the future.
Fixes#23887
I did the following manual testing:
```
$ cat ./examples/output/exit-output.yml
apiVersion: v1
kind: Pod
metadata:
labels:
name: exit
name: exit-output
spec:
restartPolicy: Never
containers:
- name: exit
image: busybox
command: ["sh", "-c", "echo Exiting in 60; sleep 60; echo goodbye"]
$ kubectl create -f ./examples/exit/exit-output.yaml
$ # wait
$ kubectl describe pod exit-output | grep State -A 4
State: Terminated
Reason: Completed
Exit Code: 0
Started: Tue, 19 Apr 2016 13:23:13 -0700
Finished: Tue, 19 Apr 2016 13:24:13 -0700
$ kubectl logs exit-output
Exiting in 60
goodbye
```
I double checked as well that the file at `/var/lib/kubelet/pods/$id/finished-$id` existed and looked as expected.
This is related to https://github.com/coreos/rkt/issues/1789#issuecomment-207111814 and follows https://github.com/kubernetes/kubernetes/pull/24367 + https://github.com/coreos/rkt/issues/2445
cc @jonboulle @iaguis @yifan-gu @kubernetes/sig-node
Automatic merge from submit-queue
stop changing the root path of the root webservice
We shouldn't mutate the root path of the root webservice (see usage). Just write the path we want.
Automatic merge from submit-queue
update controllers watching all pods to share an informer
This plumbs the shared pod informer through the various controllers to avoid duplicated watches.
Automatic merge from submit-queue
Add node e2e test for mirror pod.
This is a node e2e test for mirror pod.
After this get merged, I'll revisit the mirror pod manager PR. #18638
/cc @yujuhong
Automatic merge from submit-queue
let admission plugins indicate they want nothing
An admission plugin can return `nil, nil` for construction. This is useful for dealing with cases where the `config` passed to you effectively means, "no work". The calling code already handles this.
@derekwaynecarr
Automatic merge from submit-queue
schedulercache: remove bind() from AssumePod
Due to #24197, we make bind() asynchronous and don't need it anymore.
Submit this PR to clean it up.
Automatic merge from submit-queue
Use mCPU as CPU usage unit, add version in PerfData, and fix memory usage bug.
Partially addressed #24436.
This PR:
1) Change the CPU usage unit to "mCPU"
2) Add version in PerfData, and perfdash will only support the newest version now.
3) Fix stupid mistake when calculating the memory usage average.
/cc @vishh
Automatic merge from submit-queue
Enforce --max-pods in kubelet admission; previously was only enforced in scheduler
This is an ugly hack - I spent some time trying to understand what one NodeInfo has in common with the other one, but at some point decided that I just don't have time to do that.
Fixes#24262Fixes#20263
cc @HaiyangDING @lavalamp
Automatic merge from submit-queue
Intial draft on SeedProvider docs
Alsa more documentation. We need to reference the config section in the example docs. There are multiple PRs open in those docs, so at this point I do not want to make a mess.
Let me know if there are docs standard template that will make this more pretty.
Automatic merge from submit-queue
Removing KUBE_API_VERSIONS from our test scripts
We dont need to specify them.
Its an unnecessary extra change that people have to make while adding a group.
We also need this change for ubernetes.
cc @caesarxuchao @jianhuiz
This is implemented via touching a file on stop as a hook in the systemd
unit. The ctime of this file is then used to get the `finishedAt` time
in the future.
In addition, this changes the `startedAt` and `createdAt` to use the api
server's results rather than the annotations it previously used.
It's possible we might want to move this into the api in the future.
Fixes#23887
Automatic merge from submit-queue
fix relative working dirctory of KUBE_ROOT
fix relative working dirctory of `KUBE_ROOT`, do not need to change to `KUBE_ROOT` in the first place
Signed-off-by: Crazykev <zcq8989@gmail.com>
Automatic merge from submit-queue
update gb-frontend image. New image includes the change in PR # 23381.
Update to use the gcr.io/google-samples/gb-frontend:v4 image. New image includes the change in https://github.com/kubernetes/kubernetes/pull/23381.
Automatic merge from submit-queue
Disable travis on master.
There's no need for it, and it's blocking merges. Until we've got the munger ignoring travis, this should patch the problem.
ref #24628
Automatic merge from submit-queue
WIP: Proposed new PR release note template.
Initial template proposal - needs work to coexist with labels:
## ATTENTION - Release Note ack required!
Use the below `release-note` block to explain your change. Valid inputs include:
**"title"** - the release note is the title of the PR
**"none"** - No release note needed for this PR
_freeform text_ - Describe your change as a summarized release note
```release-note
...release-note block...
```
Second template proposal - replaces labels:
## ATTENTION - Release Note ack required!
Update the below named `release-note-needed` block to one of:
**\`\`\`release-note**
**\`\`\`release-note-action-required**
**\`\`\`release-note-none**
Then describe your change as a summarized release note within the block.
```release-note-needed
...release-note block...
`line` 2
```
