- 21 Apr, 2017 20 commits
-
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue More RC/RS controller logging updates We were comparing the address of the old and new RC.spec.replicas and we have to compare the values. This only affects logging. Update RS controller to match RC controller to log when spec.replicas changes, not status.replicas. @kargakis @janetkuo @sttts @liggitt
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue client-go PortForwarder: don't log an error if net.Listen fails **What this PR does / why we need it**: If ipv6 is disabled the client-go PortForwarder logs an error: ``` E0406 17:26:06.983609 29625 portforward.go:209] Unable to create listener: Error listen tcp6 [::1]:30143: socket: address family not supported by protocol ``` This pull request removes this error log. Reasons: * Tunnel creation might still succeed on ipv4 and the error just confuses the user (see https://github.com/kubernetes/helm/issues/2223). * If the tunnel can't be created the error gets also loggen in `listenOnPort`. * runtime.HandleError should only be used on errors "_when a non-user facing piece of code cannot return an error"_ which isn't the case here. **Which issue this PR fixes** Fixes https://github.com/kubernetes/helm/issues/2223
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Minor cleanups Minor improvements: - `ValidateNoNewFinalizers`: remove unused const - Mention that mutation of `spec.initContainers[*].image` field is allowed - Improve godoc comments
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Print conditions of RC/RS in 'kubectl describe' command **What this PR does / why we need it**: If conditions of RC/RS exist, print them in 'kubectl describe' command. **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 Print conditions of RC/RS in 'kubectl describe' command. ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue client-go workqueue example Demonstrates how to compose a controller out of cache.Controller, cache.Indexer and a workqueue.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Add nonResourceURL wildcard coverage tests Ensure `*` covering all paths is tested
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Lower allowed loss limit for Stackdriver Logging load tests
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Replace variable name to be more go friendly.
-
Wojciech Tyczynski authored
Fix issue #44757: Flaky Test_AttachDetachControllerRecovery
-
Mik Vyatskov authored
-
Andy Goldstein authored
We were comparing the address of the old and new RC.spec.replicas and we have to compare the values. This only affects logging. Update RS controller to match RC controller to log when spec.replicas changes, not status.replicas.
-
Tomas Smetana authored
-
Roman Mohr authored
Demonstrates how to compose a controller out of cache.Controller, cache.Indexer and a workqueue.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 41498, 44487) Use len of pods in stateful set error **What this PR does / why we need it**: Sync stateful set reports wrong error, we need to fix it. **Release note**: ```release-note `NONE` ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue cinder: Add support for the KVM virtio-scsi driver **What this PR does / why we need it**: The VirtIO SCSI driver for KVM changes the way disks appear in /dev/disk/by-id. This adds support for the new format. Without this, volume attaching on an openstack cluster using this kvm driver doesn't work **Special notes for your reviewer**: Does this need e2e tests? I couldn't find anywhere to add another openstack configuration used in the e2e tests. Wiki page about this: https://wiki.openstack.org/wiki/Virtio-scsi-for-bdm **Release note**: ```release-note cinder: Add support for the KVM virtio-scsi driver ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Update kubelet to use the network-plugin-dir if the cni-bin-dir flag is not set. This is a fix for the regession raised in issue #44683 **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 ```
-
Humble Chirammal authored
Signed-off-by:Humble Chirammal <hchiramm@redhat.com>
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Mark Stackdriver Logging e2e tests with a feature Makes Stackdriver Logging e2e tests, except for the most basic one, run in the separate tests suites, prepared by https://github.com/kubernetes/test-infra/pull/2542
-
xiangpengzhao authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue De-Flake Volume E2E: force GCEPD detach to prevent timeout **What this PR does / why we need it**: Fix flake`[k8s.io] Volumes [Volume] [k8s.io] PD should be mountable [Flaky] 5m38s. Flake occurs as a result of an automated detach taking longer than 5 minutes, which exceeds the timeout limit of the delete function. This PR adds explicit detach and wait func calls before the deletion. By forcing the detach and giving GCE an appropriate timeout limit, this should squash the timeout flake. This also significantly shortens cleanup time. This PR does not remove the [Flaky] tag. Once this PR is merged, I'll keep an eye on the test grid for ~1 week. If no flakes surface, I'll submit a PR to pull the tag off. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #43977 **Release note**: ```release-note NONE ```
-
- 20 Apr, 2017 20 commits
-
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 44722, 44704, 44681, 44494, 39732) Fix issue #34242: Attach/detach should recover from a crash When the attach/detach controller crashes and a pod with attached PV is deleted afterwards the controller will never detach the pod's attached volumes. To prevent this the controller should try to recover the state from the nodes status and figure out which volumes to detach. This requires some changes in the volume providers too: the only information available from the nodes is the volume name and the device path. The controller needs to find the correct volume plugin and reconstruct the volume spec just from the name. This required a small change also in the volume plugin interface. Fixes Issue #34242. cc: @jsafrane @jingxu97
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 44722, 44704, 44681, 44494, 39732) Don't rebuild endpoints map in iptables kube-proxy all the time. @thockin - i think that this PR should help with yours https://github.com/kubernetes/kubernetes/pull/41030 - it (besides performance improvements) clearly defines when update because of endpoints is needed. If we do the same for services (I'm happy to help with it), i think it should be much simpler. But please take a look if it makes sense from your perspective too.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 44722, 44704, 44681, 44494, 39732) prevent installation of docker from upstream **What this PR does / why we need it**: Disallows installation of upstream docker from PPA in the Juju kubernetes-worker charm. **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 Disallows installation of upstream docker from PPA in the Juju kubernetes-worker charm. ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 44722, 44704, 44681, 44494, 39732) delete unuse const delete unuseful const
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Redirect some test spam to files instead of main log files Ref #44707 @kubernetes/test-infra-maintainers @wojtek-t
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Use const value for pod's conditions None
-
Jess Frazelle authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 44594, 44651) remove strings.compare(), use string native operation I notice we use strings.Compare() in some code, we can remove it and use native operation.
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Delete deprecated node phase in kubect describe node. **What this PR does / why we need it**: Since NodePhase is no longer used, delete it in `kubect describe node` result. **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**: ref: https://github.com/kubernetes/kubernetes/pull/44388 **Release note**: ```release-note NONE ```
-
Rye Terrell authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 42177, 42176, 44721) Removed fluentd-gcp manifest pod ```release-note Fluentd manifest pod is no longer created on non-registered master when creating clusters using kube-up.sh. ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 42177, 42176, 44721) Job: Respect ControllerRef **What this PR does / why we need it**: This is part of the completion of the [ControllerRef](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/controller-ref.md) proposal. It brings Job into full compliance with ControllerRef. See the individual commit messages for details. **Which issue this PR fixes**: This ensures that Job does not fight with other controllers over control of Pods. Ref: #24433 **Special notes for your reviewer**: **Release note**: ```release-note Job controller now respects ControllerRef to avoid fighting over Pods. ``` cc @erictune @kubernetes/sig-apps-pr-reviews
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 42177, 42176, 44721) CronJob: Respect ControllerRef **What this PR does / why we need it**: This is part of the completion of the [ControllerRef](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/controller-ref.md) proposal. It brings CronJob into compliance with ControllerRef. See the individual commit messages for details. **Which issue this PR fixes**: This ensures that other controllers do not fight over control of objects that a CronJob owns. **Special notes for your reviewer**: **Release note**: ```release-note CronJob controller now respects ControllerRef to avoid fighting with other controllers. ``` cc @erictune @kubernetes/sig-apps-pr-reviews
-
Mik Vyatskov authored
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue (batch tested with PRs 44555, 44238) openstack: remove field flavor_to_resource I believe there is no usage about `flavor_to_resource`, and I think there is no need to build that information, too. cc @anguslees **Release note:** ``` NONE ```
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Remove the old docker-multinode files that were built into the hyperkube image **What this PR does / why we need it**: ref: https://goo.gl/VxSaKx **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 The hyperkube image has been slimmed down and no longer includes addon manifests and other various scripts. These were introduced for the now removed docker-multinode setup system. ``` cc @jbeda @brendandburns @bgrant0607 @justinsb @mikedanese
-
Kubernetes Submit Queue authored
Automatic merge from submit-queue Switch to pointer to policy rule, visit and short circuit during authorization Ref #40015 * Switches policy rule helper methods to work with pointers * Switches authorization to use a short-circuiting visitor Best-case, authorization short-circuits early and avoids accumulating rules it never needs to check Worst-case (a forbidden request), it still checks all the applicable rules, but requires less allocation to do so $ go test ./plugin/pkg/auth/authorizer/rbac/... -bench=. -benchmem -run Bench on master: ``` BenchmarkAuthorize/allow_list_pods-8 300000 4373 ns/op 3840 B/op 26 allocs/op BenchmarkAuthorize/allow_update_pods/status-8 300000 5121 ns/op 3840 B/op 26 allocs/op BenchmarkAuthorize/forbid_educate_dolphins-8 300000 4706 ns/op 3840 B/op 26 allocs/op ``` with short-circuiting and policy rule pointer changes: ``` BenchmarkAuthorize/allow_list_pods-8 2000000 930 ns/op 64 B/op 2 allocs/op BenchmarkAuthorize/allow_update_pods/status-8 1000000 1656 ns/op 64 B/op 2 allocs/op BenchmarkAuthorize/forbid_educate_dolphins-8 500000 3395 ns/op 1488 B/op 25 allocs/op ```
-
Anthony Yeh authored
-
Jordan Liggitt authored
-
Jordan Liggitt authored
-