- 09 Aug, 2017 16 commits
-
-
Jacob Beacham authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix sort-by output problem Fixes https://github.com/kubernetes/kubectl/issues/43 This bug was original introduced in pr here: https://github.com/kubernetes/kubernetes/pull/46265, I think next time if we touch something printer related package, maybe should let @smarterclayton have a review, although he is pretty busy I guess : ) and that package also changed a lot recently since he's been working on refactoring. this is a quick and dirty fix, not sure if there's better way, I will add some regression test soon... @kubernetes/sig-cli-pr-reviews ```release-note NONE ``` /assign @mengqiy /assign @smarterclayton
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Support exec/attach/portforward in `kubectl proxy` Use the UpgradeAwareProxy shared code in kubectl proxy. Provide a separate transport for those requests that does not have HTTP/2 enabled. Refactor the code to be a bit cleaner in places and to better separate changes. Fixes #32026 ```release-note `kubectl proxy` will now correctly handle the `exec`, `attach`, and `portforward` commands. You must pass `--disable-filter` to the command in order to allow these endpoints. ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Use variadic nature of *cobra.Command.AddCommand to add group of commands to a parent command **What this PR does / why we need it**: Rather than looping over commands in a group and add it one by one to a parent command, use variadic nature of *cobra.Command.AddCommand to add the group of commands to the parent.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Ensure that pricing expander is used by default in Cluster Autoscaler Pricing expander was set as the default one for GCP, however on some occasion it was possible that AUTOSCALER_EXPANDER_CONFIG variable was not set resulting in using the the random expander.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 50173, 50324, 50288, 50263, 50333) Add debug logs to log-dump ref https://github.com/kubernetes/test-infra/issues/3981 cc @fejta @krzyzacy
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 50173, 50324, 50288, 50263, 50333) Copy annotations from StatefulSet to owned ControllerRevisions **What this PR does / why we need it**: This PR starts copying annotations from a `StatefulSet`'s metadata to the `ControllerRevision`s it owns. `DaemonSet` controller copies the annotations from a `DaemonSet`s metadata to the `ControllerRevision`s it owns. One of the annotation copied is `kubernetes.io/change-cause`, which is used in `DaemonSetHistoryViewer` to fill in the `CHANGE-CAUSE` column of revision history of a `DaemonSet`. For consistency, the `StatefulSet` controller should do the same, i.e., copy annotations in a `StatefulSet`'s metadata to the `ControllerRevision`s it owns for consistency. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #50158. **Special notes for your reviewer**: /assign @kow3ns **Release note**: ```release-note Copy annotations from a StatefulSet's metadata to the ControllerRevisions it owns ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 50173, 50324, 50288, 50263, 50333) Honor --use-service-account-credentials and warn when missing private key Fixes #50275 by logging a warning and failing to start rather than continue to run ignoring the user's specified config
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 50173, 50324, 50288, 50263, 50333) Add blank import for node tests The node tests weren't being run because the weren't imported in the test/e2e/e2e_test.go file. Thanks to @abgworrall for sounding the alarm (he noticed [sig-node] wasn't in the test results)! /assign @yujuhong /cc @abgworrall
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue kubeadm: Centralize commonly used paths/constants to the constants pkg **What this PR does / why we need it**: Before there were constants defined for the control plane components in three different places: - images - phases/controlplane - phases/selfhosting Now they are in one centralized place. I also moved funcs for building common paths to that lib. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # Dependency for: https://github.com/kubernetes/kubernetes/pull/48899 **Special notes for your reviewer**: Most of this PR really is autogenerated with a replace tool. I tested this and things work just normally as well. **Release note**: ```release-note NONE ``` @timothysc @dmmcquay @pipejakob @kubernetes/sig-cluster-lifecycle-pr-reviews
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Fix local storage test failures **What this PR does / why we need it**: Fixed a few issues: - CI environment on GCE cannot resolve node names, need to use IPs. Use a different SSH wrapper that will get the IPs from the node object. - Use hostdir instead of containerdir now that commands are executed directly on the host, instead of through a container. - Get the PVC object again after it is bound so that it has the PV name. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #50128 **Release note**: NONE /release-note-none /sig storage
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Change default update strategy to rolling update Fixes https://github.com/kubernetes/kubernetes/issues/49604 Change default update strategy to rolling update for daemonset and statefulset in v1beta2 cc @kubernetes/sig-apps-pr-reviews @lukaszo @kargakis **Release note**: ```release-note Make rolling update the default update strategy for v1beta2.DaemonSet and v1beta2.StatefulSet ```
-
caleb miles authored
owners: remove euank from sig-node-reviewers
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add waitForFailure for e2e test framework **What this PR does / why we need it**: Add waitForFailure for e2e test framework, this could reduce the reliance on logs. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: Part of #44118. Refer https://github.com/kubernetes/kubernetes/pull/48858#discussion_r128331726 **Special notes for your reviewer**: **Release note**: ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue kubectl: deploy generators don't need to impl Generator iface The `kubectl create deployment` generators do not need to implement the Generator interface, since they are only used as implementations of the StructuredGenerator interface. I was able to delete some tests of their Generator methods as part of this change. ### Considerations for code reviewers 1. Every other StructuredGenerator implementation implements the Generator interface in additional. My change makes the "create deployment" generators a little unusual. I've added a docstring to this effect in `util/factory_client_access.go`. 2. This significantly reduces the maintenance / testing burden for future updates to `kubectl create deployment`. **Release note**: ```release-note NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Deprecate Deployment .spec.rollbackTo field ~Depends on #48746~ (merged) xref: #46934, #49135 1. Deprecate Deployment field `.spec.rollbackTo` in `extensions/v1beta1` and `apps/v1beta1`, and remove the same field and `/rollback` endpoint from `apps/v1beta2` Deployment. 1. Add an annotation `deprecated.deployment.rollback.to` in `apps/v1beta2` for conversion to/from other versions. Note: `apps/v1beta2` is new in 1.8 (and WIP), so it is okay to make breaking changes to it. ```release-note Deprecate Deployment .spec.rollbackTo field ```
-
- 08 Aug, 2017 24 commits
-
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Added monitoring sidecar for Heapster
-
Anirudh authored
-
Anirudh authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Change test to work around restmapper pluralization bug Fixes https://github.com/kubernetes/kubernetes/issues/50022 Works around the pluralization bug to unblock the queue. Once the restmapper bug is fixed in https://github.com/kubernetes/kubernetes/pull/50012, we should add tests specifically for unconventional singular/plural word endings.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Block on master-creation step for large clusters (>50 nodes) in kube-up I recently noticed a failure in our 5000-node scale test where the master failed to initialize within time. But it went on and created all 5000 nodes due to not blocking on master creation. Turned out the master VM wasn't even created: ``` W0808 10:00:49.340] ERROR: (gcloud.compute.instances.create) Could not fetch resource: ... Try a different zone, or try again later. ``` Even some of our 100-node tests are flaking occasionally during cluster startup (with master validation step timing out) and I think the reason is the same (issue - https://github.com/kubernetes/kubernetes/issues/49453) We should block on that step for large clusters. cc @kubernetes/sig-scalability-misc @gmarek
-
Shyam Jeedigunta authored
-
Yinan Li authored
-
Marcin Wielgus authored
-
Michael Taufen authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add a simple cloud provider for e2e tests on kubemark **What this PR does / why we need it**: Adds a simplified cloud provider for kubemark. This enables us to add and remove nodes and operate on nodegroups while running tests on kubemark. This is needed to run scalability tests for cluster autoscaler on kubemark. See https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/proposals/kubemark_integration.md **Release note**: ``` NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 48068, 49587) DNS name error message improvement **What this PR does / why we need it**: Small error message fix. The error message misled me slightly / would have saved time if correct **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # n/a **Special notes for your reviewer**: n/a **Release note**: n/a
-
Shyam Jeedigunta authored
-
Lucas Käldström authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add e2e test for cronjob chained removal This is test proving https://github.com/kubernetes/kubernetes/pull/44058 works with cronjobs. This will fail until the aforementioned PR merges. @caesarxuchao ptal
-
Piotr Szczesniak authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue complete and correct code comment **What this PR does / why we need it**: **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # **Special notes for your reviewer**: **Release note**: ```release-note ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 50254, 50174, 50179) Moved node/testutil to upper dir. **What this PR does / why we need it**: Moved node/testutil to upper directory (`pkg/controller`); it's used by several controllers, and we need to test some helper func in `pkg/controller`. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: part of #49522 **Release note**: ```release-note N/A ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 50254, 50174, 50179) kubeadm: Add back labels for the Static Pod control plane **What this PR does / why we need it**: This Labels section has been removed now for a short period during the v1.8 dev cycle, but I found a good use-case for it; namely filtering Mirror Pods by the `component=kube-*` label when waiting for the self-hosted control plane to come up after an upgrade. It's not _really_ neccessary, but nice to have. Also noticed the lack of coverage for this func, so added a small unit test. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # Dependency for: https://github.com/kubernetes/kubernetes/pull/48899 **Special notes for your reviewer**: **Release note**: ```release-note NONE ``` @kubernetes/sig-cluster-lifecycle-pr-reviews @dmmcquay @timothysc @mattmoyer
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 50254, 50174, 50179) Revert "Merge pull request #47353 from apelisse/http-cache" Some issues were discovered with the caching merged in #47353: * uses a disk-based cache that is not safe between processes (does not use atomic fs operations) * writes get/list responses to disk that should not be cached (like `kubectl get secrets`) * is vulnerable to partially written cache responses being used as responses to future requests * breaks uses of the client transport that make use of websockets * defaults to enabling the cache for any client builder using RecommendedConfigOverrideFlags or DefaultClientConfig which affects more components than just kubectl This reverts commit fc89743d, reversing changes made to 29ab38e8.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 45993, 50293) Add error return for the Marshal object invocation. Add error return for the Marshal object invocation. **Release note**: ``` None ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 45993, 50293) [Federation] HPA controller This PR implements the design listed in https://github.com/kubernetes/community/pull/593. This is still a work in progress, and needs more unit tests to be added. I will add the integration tests and e2e tests in a separate PR(s). @kubernetes/sig-federation-pr-reviews **Release note**: ``` Horizontal Pod Autoscaling is now available as an alpha feature in federation. It can be used to distribute and scale workload across clusters joined in a federation. In its current form, it works only on cpu utilization and the support for other metrics is yet to be built in. ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 50208, 50259, 49702, 50267, 48986) Relax restrictions on environment variable names. Fixes #2707 The POSIX standard restricts environment variable names to uppercase letters, digits, and the underscore character in shell contexts only. For generic application usage, it is stated that all other characters shall be tolerated. (Reference [here](http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap08.html), my prose reasoning [here](https://github.com/kubernetes/kubernetes/issues/2707#issuecomment-285309156).) This change relaxes the rules to some degree. Namely, we stop requiring environment variable names to be strict `C_IDENTIFIERS` and start permitting lowercase, dot, and dash characters. Public container images using environment variable names beyond the shell-only context can benefit from this relaxation. Elasticsearch is one popular example.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 50208, 50259, 49702, 50267, 48986) Move ownership of proxy test to sig-network directory ```release-note None ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 50208, 50259, 49702, 50267, 48986) fix the typo of intializing **What this PR does / why we need it**: **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # **Special notes for your reviewer**: **Release note**: ```release-note NONE ```
-