- 22 May, 2016 3 commits
-
-
k8s-merge-robot authored
Automatic merge from submit-queue Introduce node memory pressure condition to scheduler Following the work done by @derekwaynecarr at https://github.com/kubernetes/kubernetes/pull/21274, introducing memory pressure predicate for scheduler. Missing: * write down unit-test * test the implementation At the moment this is a heads up for further discussion how the new node's memory pressure condition should be handled in the generic scheduler. **Additional info** * Based on [1], only best effort pods are subject to filtering. * Based on [2], best effort pods are those pods "iff requests & limits are not specified for any resource across all containers". [1] https://github.com/derekwaynecarr/kubernetes/blob/542668cc7998fe0acb315a43731e1f45ecdcc85b/docs/proposals/kubelet-eviction.md#scheduler [2] https://github.com/kubernetes/kubernetes/pull/14943
-
k8s-merge-robot authored
Automatic merge from submit-queue Heredoc fix on k8sm ha document Fix for a missing delimiter on a heredoc in contrib/mesos/docs/ha.md. []()
-
k8s-merge-robot authored
Automatic merge from submit-queue azure: azkube v0.0.5 + deploy kube-system + hack/ script for hyperkube Update the Azure bring up. Also added a script `hack/dev-push-hyperkube.sh` for fast iteration on changes. One can deploy a cluster with a given hyperkube image reference and then use this script to rapidly iterate on changes. Testing changes just requires pulling the updated hyperkube image on the boxes and then cycling kubelet/docker or restarting the node. <!-- Reviewable:start --> --- This change is [<img src="http://reviewable.k8s.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](http://reviewable.k8s.io/reviews/kubernetes/kubernetes/23344) <!-- Reviewable:end -->
-
- 21 May, 2016 35 commits
-
-
k8s-merge-robot authored
Automatic merge from submit-queue Fix detection of docker cgroup on RHEL Check docker's pid file, then fallback to pidof when trying to determine the pid for docker. The latest docker RPM for RHEL changes /usr/bin/docker from an executable to a shell script (to support /usr/bin/docker-current and /usr/bin/docker-latest). The pidof check for docker fails in this case, so we check /var/run/docker.pid first (the default location), and fallback to pidof if that fails. @kubernetes/sig-node @kubernetes/rh-cluster-infra
-
k8s-merge-robot authored
Automatic merge from submit-queue Add init containers to PSP admission Treat them just like regular containers. @pweil-
-
Cole Mickens authored
-
Cole Mickens authored
-
Jan Chaloupka authored
Scheduler: introduce CheckNodeMemoryPressurePredicate, don't schedule pods for nodes that reports memory pressury. Introduce unit-test for CheckNodeMemoryPressurePredicate Following work done in #14943
-
k8s-merge-robot authored
Automatic merge from submit-queue ScheduledJob client @erictune SheduledJob part 2, based on #24970 so first two commits doesn't count. This is still WIP, but it's here so you know :) ```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). ``` []()
-
k8s-merge-robot authored
Automatic merge from submit-queue cluster/gce/coreos: Set service-cluster-ip-range Broken by #19242 See also #26002 This is necessary to kube-up for me, but depending on how #26002 plays out, this PR might not be necessary. Happy to close this or merge or whatever depending on what's best. cc @yifan-gu @sjpotter @mikedanese
-
k8s-merge-robot authored
Automatic merge from submit-queue Add support for limiting grace period during soft eviction Adds eviction manager support in kubelet for max pod graceful termination period when a soft eviction is met. ```release-note Kubelet evicts pods when available memory falls below configured eviction thresholds ``` /cc @vishh
-
k8s-merge-robot authored
Automatic merge from submit-queue Use protobufs by default to communicate with apiserver (still store JSONs in etcd) @lavalamp @kubernetes/sig-api-machinery
-
k8s-merge-robot authored
Automatic merge from submit-queue Cache Webhook Authentication responses Add a simple LRU cache w/ 2 minute TTL to the webhook authenticator. Kubectl is a little spammy, w/ >= 4 API requests per command. This also prevents a single unauthenticated user from being able to DOS the remote authenticator.
-
k8s-merge-robot authored
Automatic merge from submit-queue Update rkt API version to 1.6.0 Updates coreos/rkt container runtime dependency to `1.6.0` Fixes #25430
-
k8s-merge-robot authored
Automatic merge from submit-queue Add NetworkPolicy API Resource API implementation of https://github.com/kubernetes/kubernetes/pull/24154 Still to do: - [x] Get it working (See comments) - [x] Make sure user-facing comments are correct. - [x] Update naming in response to #24154 - [x] kubectl / client support - [x] Release note. ```release-note Implement NetworkPolicy v1beta1 API object / client support. ``` Next Steps: - UTs in separate PR. - e2e test in separate PR. - make `Ports` + `From` pointers to slices (TODOs in code - to be done when auto-gen is fixed) CC @thockin []()
-
k8s-merge-robot authored
Automatic merge from submit-queue Adding support objects for integrating dynamic client the kubectl builder Kubectl will try to decode into `runtime.VersionedObjects`, so the `UnstructuredJSONScheme` needs to handle that intelligently. Kubectl's builder also needs a `meta.RESTMapper` and `runtime.Typer`. The `meta.RESTMapper` requires a `runtime.ObjectConvertor` (spelling?) that works with `runtime.Unstructured`. The mapper and typer required discovery info, so I just put that in the kubectl util package since it didn't really seem to fit anywhere else. Subsequent PRs will be using these in kubectl. cc @kubernetes/sig-api-machinery @smarterclayton @liggitt @lavalamp
-
Maciej Szulik authored
-
Maciej Szulik authored
-
Maciej Szulik authored
-
Maciej Szulik authored
-
Maciej Szulik authored
-
k8s-merge-robot authored
Automatic merge from submit-queue Add support for PersistentVolumeClaim in Attacher/Detacher interface The attach detach interface does not support volumes which are referenced through PVCs. This PR adds that support
-
k8s-merge-robot authored
Automatic merge from submit-queue Only expose top N images in `NodeStatus` Fix #25209 Sorted the image and only pick set top 50 sized images in node status. cc @vishh
-
k8s-merge-robot authored
Automatic merge from submit-queue Extend secrets volumes with path control As per [1] this PR extends secrets mapped into volume with: * key-to-path mapping the same way as is for configmap. E.g. ``` { "apiVersion": "v1", "kind": "Pod", "metadata": { "name": "mypod", "namespace": "default" }, "spec": { "containers": [{ "name": "mypod", "image": "redis", "volumeMounts": [{ "name": "foo", "mountPath": "/etc/foo", "readOnly": true }] }], "volumes": [{ "name": "foo", "secret": { "secretName": "mysecret", "items": [{ "key": "username", "path": "my-username" }] } }] } } ``` Here the ``spec.volumes[0].secret.items`` added changing original target ``/etc/foo/username`` to ``/etc/foo/my-username``. * secondly, refactoring ``pkg/volumes/secrets/secrets.go`` volume plugin to use ``AtomicWritter`` to project a secret into file. [1] https://github.com/kubernetes/kubernetes/blob/master/docs/design/configmap.md#changes-to-secret -
Wojciech Tyczynski authored
-
k8s-merge-robot authored
Automatic merge from submit-queue volume recycler: Don't start a new recycler pod if one already exists. Recycling is a long duration process and when the recycler controller is restarted in the meantime, it should not start a new recycler pod if there is one already running. This means that the recycler pod must have deterministic name based on name of the recycled PV, we then get name conflicts when creating the pod. Two things need to be changed: - recycler controller and recycler plugins must pass the PV.Name to place, where the pod is created. This is most of the patch and it should be pretty straightforward. - create recycler pod with deterministic name and check "already exists" error. When at it, remove useless 'resourceVersion' argument and make log messages starting with lowercase. There is an unit test to check the behavior + there is an e2e test that checks that regular recycling is not broken (it does not try to run two recycler pods in parallel as the recycler is single-threaded now).
-
k8s-merge-robot authored
Automatic merge from submit-queue Update upstream remote regex I've fixed the upstream remote regex so that it properly recognizes ssh link, like this one: ``` upstream git@github.com:kubernetes/kubernetes.git (fetch) ``` []()
-
k8s-merge-robot authored
Automatic merge from submit-queue Add PV test to persistent volume integration test This is a follow-up to #25120 @kubernetes/sig-storage
-
k8s-merge-robot authored
Automatic merge from submit-queue Hook rkt kubelet runtime up to network plugins
-
k8s-merge-robot authored
Automatic merge from submit-queue cluster/gce/coreos: Update addon manifests. cc @yujuhong @timstclair @ArtfulCoder
-
k8s-merge-robot authored
Automatic merge from submit-queue etcd3/compactor: fix logging endpoints Missed a logging.
-
k8s-merge-robot authored
Automatic merge from submit-queue Updaing QoS policy to be at the pod level Quality of Service will be derived from an entire Pod Spec, instead of being derived from resource specifications of individual resources per-container. A Pod is `Guaranteed` iff all its containers have limits == requests for all the first-class resources (cpu, memory as of now). A Pod is `BestEffort` iff requests & limits are not specified for any resource across all containers. A Pod is `Burstable` otherwise. Note: Existing pods might be more susceptible to OOM Kills on the node due to this PR! To protect pods from being OOM killed on the node, set `limits` for all resources across all containers in a pod. <!-- Reviewable:start --> --- This change is [<img src="http://reviewable.k8s.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](http://reviewable.k8s.io/reviews/kubernetes/kubernetes/14943) <!-- Reviewable:end -->
-
k8s-merge-robot authored
Automatic merge from submit-queue Check status of framework.CheckPodsRunningReady Check status of framework.CheckPodsRunningReady and fail test if it's false, instead of silently ignoring the failure. This doesn't fix whatever is causing the pod not to start in #17523 but it does fail the test as soon as it detects the pod didn't start, instead of allowing the testing to proceed. cc @kubernetes/sig-testing @spxtr @ixdy @kubernetes/rh-cluster-infra
-
k8s-merge-robot authored
Automatic merge from submit-queue Pre-pull images in node e2e-tests. Possible resolution for #24905 []()
-
k8s-merge-robot authored
Automatic merge from submit-queue Updating CentOS image, adding heat back to the required cli tools. []() Updated the CentOS cloudimage to the latest available, and also added heat to the required list of cli tools. This is an interim step to replacing all the commands with openstackclient.
-
k8s-merge-robot authored
Automatic merge from submit-queue Proposal for disk based evictions cc @dchen1107 @derekwaynecarr
-
Andy Goldstein authored
Check status of framework.CheckPodsRunningReady and fail test if it's false, instead of silently ignoring the failure.
-
Euan Kemp authored
-
- 20 May, 2016 2 commits
-
-
Mike Danese authored
Implement OIDC client AuthProvider
-
Mike Danese authored
Update node e2e containervm image to not start kubelet as part of ini…
-