Kubernetes Submit Queue 0042ce5684 Merge pull request #36892 from gmarek/nodecontroller ...

Automatic merge from submit-queue

Add logs near force deletions of Pods

We should always log something when control plane force deletes the Pod.

@davidopp I think that logging force deletions is enough, or do you think we should log soft deletions as well?

cc @deads2k

2016-11-20 16:00:10 -08:00

..

certificates

include multiple versions in clientset

2016-10-29 13:30:47 -07:00

cronjob

Change ScheduledJob POD name suffix from hash to Unix Epoch

2016-11-15 17:25:32 +01:00

daemon

Merge pull request #35465 from lukaszo/ds_event

2016-11-07 18:18:05 -08:00

deployment

Merge pull request #36579 from kargakis/restore-events-for-tests

2016-11-11 15:50:31 -08:00

disruption

Add observedGeneration to PodDisruptionBudgetStatus

2016-11-08 17:06:17 +01:00

endpoint

Rename PetSet API to StatefulSet

2016-10-27 17:25:10 -07:00

garbagecollector

Replace negotiation with a new method that can extract info

2016-10-28 11:30:11 -04:00

informers

Switch to JobLister

2016-11-03 20:41:40 -04:00

job

Switch to JobLister

2016-11-03 20:41:40 -04:00

namespace

Fix possible race in operationNotSupportedCache

2016-11-04 14:11:54 -04:00

node

Add logs near force deletions of Pods

2016-11-16 15:00:01 +01:00

petset

implement statefulset update pet unit test

2016-11-05 19:47:01 +08:00

podautoscaler

More unittests for HPA.

2016-11-10 17:30:23 +01:00

podgc

Add logs near force deletions of Pods

2016-11-16 15:00:01 +01:00

replicaset

Replica set/rc controller changes for Conditions

2016-11-02 10:30:09 +01:00

replication

Replica set/rc controller changes for Conditions

2016-11-02 10:30:09 +01:00

resourcequota

Use available informers in quota replenishment

2016-11-06 18:45:36 -05:00

route

autogenerated

2016-10-21 17:32:32 -07:00

service

include multiple versions in clientset

2016-10-29 13:30:47 -07:00

serviceaccount

convert SA controller to shared informers

2016-10-27 15:44:46 -04:00

volume

Merge pull request #37038 from ymqytw/retry_old_patch_after_new_patch_fail

2016-11-19 01:02:47 -08:00

.import-restrictions

…

BUILD

include multiple versions in clientset

2016-10-29 13:30:47 -07:00

client_builder.go

move watch.ListWatchUntil to its own package to avoid future import cycle

2016-10-30 13:14:20 -07:00

controller_ref_manager.go

…

controller_utils_test.go

…

controller_utils.go

controller: support perma-failed deployments

2016-11-04 13:36:46 +01:00

doc.go

…

lookup_cache.go

…

OWNERS

…