- 08 Nov, 2016 14 commits
-
-
Jerzy Szczepkowski authored
Added e2e test for HA master replicas in different zones.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix non-default etcd image handling in kubemark Doesn't touch production code.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Deleting dead code from federation service controller
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Node Conformance Test: Containerize the node e2e test For #30122, #30174. Based on #32427, #32454. **Please only review the last 3 commits.** This PR packages the node e2e test into a docker image: - 1st commit: Add `NodeConformance` flag in the node e2e framework to avoid starting kubelet and collecting system logs. We do this because: - There are all kinds of ways to manage kubelet and system logs, for different situation we need to mount different things into the container, run different commands. It is hard and unnecessary to handle the complexity inside the test suite. - 2nd commit: Remove all `sudo` in the test container. We do this because: - In most container, there is no `sudo` command, and there is no need to use `sudo` inside the container. - It introduces some complexity to use `sudo` inside the test. (https://github.com/kubernetes/kubernetes/issues/29211, https://github.com/kubernetes/kubernetes/issues/26748) In fact we just need to run the test suite with `sudo`. - 3rd commit: Package the test into a docker container with corresponding `Makefile` and `Dockerfile`. We also added a `run_test.sh` script to start kubelet and run the test container. The script is only for demonstration purpose and we'll also use the script in our node e2e framework. In the future, we should update the script to start kubelet in production way (maybe with `systemd` or `supervisord`). @dchen1107 @vishh /cc @kubernetes/sig-node @kubernetes/sig-testing **Release note**: <!-- Steps to write your release note: 1. Use the release-note-* labels to set the release note state (if you have access) 2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. --> ``` release-note Release alpha version node test container gcr.io/google_containers/node-test-ARCH:0.1 for users to verify their node setup. ```
-
Wojciech Tyczynski authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Adding cadcading deletion support for federated secrets Ref https://github.com/kubernetes/kubernetes/issues/33612 Adding cascading deletion support for federated secrets. The code is same as that for namespaces. Just ensuring that DeletionHelper functions are called at right places in secret_controller. Also added e2e tests. cc @kubernetes/sig-cluster-federation @caesarxuchao ```release-note federation: Adding support for DeleteOptions.OrphanDependents for federated secrets. Setting it to false while deleting a federated secret also deletes the corresponding secrets from all registered clusters. ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue kuberuntime: remove unused GetNs code
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Deploy kube-dns with cluster-proportional-autoscaler This PR integrates [cluster-proportional-autoscaler](https://github.com/kubernetes-incubator/cluster-proportional-autoscaler) with kube-dns for DNS horizontal autoscaling. Fixes #28648 and #27781.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue CRI: Add security context for sandbox/container Part of #29478. This PR - adds security context for sandbox and fixes #33139 - encaps container security context to `SecurityContext` and adds missing features - Note that capability is not fully accomplished in this PR because it is under discussion at #33614. cc/ @yujuhong @yifan-gu @Random-Liu @kubernetes/sig-node
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Emit event when scheduling daemon fails
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix kubectl drain for statefulset Support deleting pets for `kubectl drain`. Use evict to delete pods. Fixes: #33727 ```release-note Adds support for StatefulSets in kubectl drain. Switches to use the eviction sub-resource instead of deletion in kubectl drain, if server supports. ``` @foxish @caesarxuchao
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Rename experimental-runtime-integration-type to experimental-cri Also rename the field in the component config to `EnableCRI`
-
ymqytw authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue copy PodInitialized condition to v1 Copied from pkg/api/types.go I might batch this change with other similar changes, but want to gets this reviewed first. cc @dchen1107 @yujuhong
-
- 07 Nov, 2016 26 commits
-
-
Random-Liu authored
-
Random-Liu authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add constants for node role labels
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Default kube-proxy to the old behavior for proxier sync. Fix #36281. This PR defaults `minSyncPeriod` to 0 and makes kube-proxy fall back to the old behavior to fix the immediate problem #36266. @bprashanth
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix config file names inside fluentd-gcp image Need this in order to merge https://github.com/kubernetes/kubernetes/pull/36358 Because on container-vm we need implicitly used configuration file @piosz
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix a data race condition in federation namespace controller Fixes https://github.com/kubernetes/kubernetes/issues/36364 Fixing federation namespace controller to create a copy of namespace fetched from the store before editing it. Without it there is a data race condition with other readers of the store. cc @kubernetes/sig-cluster-federation @mwielgus @madhusudancs
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Node Conformance Test: Mark more conformance test For https://github.com/kubernetes/kubernetes/issues/30122. This PR: 1) Removes unused image test. 2) Marks more conformance tests based on https://docs.google.com/spreadsheets/d/1yib6ypfdWuq8Ikyo-rTcBGHe76Xur7tGqCKD9dkzx0Y/edit?usp=sharing. Notice that 2 tests are not marked conformance for now: 1. **OOM score test:** The test is serial and is verifying host PID directly. The test should start a pod with PID=host and verify inside the pod. @vishh 2. **Summary api test:** The assumption made in the test doesn't always make sense for arbitrary image, for example: The fs capacity bounds is only [(100mb, 100gb)](https://github.com/kubernetes/kubernetes/blob/master/test/e2e_node/summary_test.go#L62). @timstclair 3. We should consider mark **[cgroup manager test](https://github.com/kubernetes/kubernetes/blob/master/test/e2e_node/cgroup_manager_test.go)** as conformance test. @dchen1107 @vishh @timstclair /cc @kubernetes/sig-node
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Removed EXPERIMENTAL from KUBE_REPLICATE_EXISTING_MASTER flag.
-
Yu-Ju Hong authored
-
nikhiljindal authored
-
nikhiljindal authored
-
nikhiljindal authored
-
Mik Vyatskov authored
-
Yu-Ju Hong authored
-
Zihong Zheng authored
The e2e tests cover cases like cluster size changed, parameters changed, ConfigMap got deleted, autoscaler pod got deleted, etc. They are separated into a fast part(could be run parallelly) and a slow part(put in [serial]). The fast part of the e2e tests cost around 50 seconds to run.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Enable StreamingProxyRedirects for CRI e2e tests Required for CRI attach/exec/port-forward calls.
-
Zihong Zheng authored
DNS horizontal autoscaling feature is turned on by default on gce. The corresponding env var is piped into almost all other cloud providers.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue kubectl: enhancements for deployment progress deadline Changes: * add deployment conditions in the describer * abort 'rollout status' for deployments that have exceeded their progress deadline Depends on https://github.com/kubernetes/kubernetes/pull/35691. @kubernetes/kubectl @kubernetes/deployment Fixes https://github.com/kubernetes/kubernetes/issues/31319
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue test: wait until all pods are available for newly created deployment Fixes https://github.com/kubernetes/kubernetes/issues/35337 @kubernetes/deployment
-
Tim St. Clair authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Backup before migration Do backup before etcd migration. Ref #20504
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add verify script for federation OpenAPI spec generation We are missing hack/verify-federation-openapi-spec.sh. It should be something similar to hack/verify-openapi-spec.sh.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix fluentd-gcp Dockerfile to reduce image size Change reduces image size by 150MB. @piosz
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add rescheduler logs to the fluentd-gcp configuration Fix #36227 Allows fluentd-gcp plugin to collect rescheduler logs from master node and store in the logging backend. @piosz
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix setNodeAddress in combination with cloud providers <!-- Thanks for sending a pull request! Here are some tips for you: 1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md 2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md 3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes --> **What this PR does / why we need it**: Fixes a follow-up bug introduced by https://github.com/kubernetes/kubernetes/pull/36231 The PR missed to update node.Status.Addresses in case the host name was already set by the cloud provider. fixes #36234
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Rename ScheduledJobs to CronJobs I went with @smarterclayton idea of registering named types in schema. This way we can support both the new (CronJobs) and old (ScheduledJobs) resource name. Fixes #32150. fyi @erictune @caesarxuchao @janetkuo Not ready yet, but getting close there... **Release note**: ```release-note Rename ScheduledJobs to CronJobs. ```
-