Thomas Hartland df16317a89 After handling status update, reset update timer with correct duration ...

If the ping timer is being used, it should be reset with the ping update
interval. If the status update interval is used then Ping stops being
called for long enough to cause kubernetes to mark the node as NotReady.

(cherry picked from commit c258614d8f)

2019-11-15 14:30:54 -08:00

..

api

Add unused code linter

2019-09-24 12:55:52 -07:00

doc.go

Adds Done() and Err() to pod controller (#735)

2019-09-10 17:44:19 +01:00

env_internal_test.go

misspell

2019-09-26 20:52:06 +09:00

env.go

fix a to an in annotation (#715)

2019-08-05 20:13:40 +01:00

lifecycle_test.go

Put sync lifecycle tests being -short flag.

2019-10-29 15:05:35 -07:00

mock_test.go

Re-add support for sync providers

2019-10-24 09:23:28 -07:00

node_test.go

Merge branch 'master' into upgrade-k8s-v2

2019-08-13 10:43:00 +01:00

node.go

After handling status update, reset update timer with correct duration

2019-11-15 14:30:54 -08:00

pod_test.go

Re-add support for sync providers

2019-10-24 09:23:28 -07:00

pod.go

Re-add support for sync providers

2019-10-24 09:23:28 -07:00

podcontroller_test.go

Use go-cmp to compare pods to suppress duplicate updates

2019-10-10 13:25:27 -07:00

podcontroller.go

Apply suggestions from code review

2019-10-24 09:23:33 -07:00

queue.go

Remove sync provider support

2019-10-02 09:28:09 -07:00

sync.go

[Sync Provider] Fix panic on not found pod status

2019-11-15 14:30:22 -08:00