58e6b1914c
kuryr-kubernetes watcher watches k8s resources and trigger registered pipeline. This patch handles restarting watching when watch thread has failed. Change-Id: I27a719a326dc37f97c46b88d0c171d0f12ded605 Closes-Bug: 1739776 Related-Bug: 1705429 Signed-off-by: Eunsoo Park <esevan.park@gmail.com>
22 lines
713 B
YAML
22 lines
713 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
For the kuryr kubernetes watcher,
|
|
a new option 'watch_retry_timeout' has been added.
|
|
The following should be modified at kuryr.conf::
|
|
|
|
|
|
[kubernetes]
|
|
# 'watch_retry_timeout' field is optional,
|
|
# default = 60 if not set.
|
|
watch_retry_timeout = <Time in seconds>
|
|
|
|
fixes:
|
|
- |
|
|
K8s api server is often temporarily down and restored soon in production
|
|
environment. Since kuryr-kubernetes watches k8s resources by connecting
|
|
k8s api server, watcher fails to watch the resources if k8s api server is
|
|
down.
|
|
In order to fix it, we made watcher retry connecting to k8s api server for
|
|
specific time duration when an exception is raised.
|