Brian Goff 98ca5c8398 Handle not found case for status update ...

If we don't handle the "pod not found" case then we end up with the pod
getting re-queued over and over until the max retries are hit. It also
blocks the queue for other pod status updates for that pod
namespace/name.

2019-06-04 14:39:58 -07:00

..

api

Use errdefs package

2019-06-04 14:29:23 -07:00

doc.go

Decouple vkubelet/* packages from providers (#626)

2019-05-17 17:01:05 -07:00

env_internal_test.go

Allow composing env var from existing env vars. (#643)

2019-06-01 09:41:10 -07:00

env.go

Allow composing env var from existing env vars. (#643)

2019-06-01 09:41:10 -07:00

node_test.go

Support error handler callback for node status (#648)

2019-06-01 09:46:47 -07:00

node.go

Remove usage of ocstatus package

2019-06-04 14:29:25 -07:00

pod_test.go

Use errdefs package

2019-06-04 14:29:23 -07:00

pod.go

Handle not found case for status update

2019-06-04 14:39:58 -07:00

podcontroller.go

Remove usage of ocstatus package

2019-06-04 14:29:25 -07:00

queue.go

Handle not found case for status update

2019-06-04 14:39:58 -07:00